blocks|key|1021022|text|发送/接收具有特定长度的数据，即。串口、Web请求、FTP请求。基本上是在系统的较低级别上工作的东西。此外，大多数集合都使用数组进行存储(值得注意的例外是：LinkedList<T>)。集合只是另一个抽象层。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1021023|entityMap^0|26|D|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Sending/Receiving data with a specific length comes to mind, ie. Serial Port, Web Request, FTP Request. Basically stuff that works on a lower level in the system. Also, most Collections are using an array for storage (Noteable exception: <code>LinkedList&lt;T&gt;</code>). Collections are just another abstraction layer.

blocks|key|4414256|text|数组很有用，因为它们在内存中始终是线性的，并且使用起来很快。例如，我可以将一个byte[]直接编组到一个结构中，没有任何问题，但据我所知，List<T>必须首先转换为一个数组。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4414257|entityMap^0|13|6|1X|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Arrays are useful because they are always linear in memory and are fast to work with. For example I can take a <code>byte[]</code> and marshal directly into a structure without any problems but a <code>List&lt;T&gt;</code> would have to be converted to an array first as far as I know.

blocks|key|4414214|text|是的，数组当然还有用处。有些方法仍然需要数组。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4414215|例如：|4414216|string[]+items+=+"a,b;c:d".Split(new+char[]{',',';',':'});|code-block|syntax|javascript|4414217|这仍然是保留一大堆项目的最简单方法，也是你需要一些特定功能之前的首选，比如动态增长。|4414218|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Yes, there certainly still is a use for arrays. Some methods still needs arrays.

For example:

<pre><code>string[] items = "a,b;c:d".Split(new char[]{',',';',':'});
</code></pre>

It's still the simplest way to keep a bunch of items, and the number one choice until you need some specific feature, like for example dynamic growth.

blocks|key|1764776|text|不，它们仍然有其用途，应该始终考虑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1764777|记住，数组是固定长度的非常基本的表示，所以它们非常快，大多数语言都能根据数组中使用的类型来理解它们。|1764778|您需要在创建数组时定义数组大小，并且以后不能更改它的大小。列表和其他内容可以根据需要增加，这增加了与内存分配相关的开销。|1764779|列表和其他类型很有用，因为它们可以做很多事情，但有时您不需要所有这些额外的开销，所以您只需要一个数组。|1764780|这就像驾驶一辆4x4，因为你认为有一天你可能需要离开公路，即使有99.9%25的机会你会在正常的道路上。数组将是基本的汽车，例如列表将是4x4...它可以做汽车能做的一切(引擎盖下的可能使用大多数相同的部件)，但以汽油为代价，成本，可能不适合某些停车位，等等。|1764781|数组=性能和兼容性|1764782|列表(或其他表示)=以牺牲性能和兼容性为代价的易用性|1764783|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

No they still have their uses and should always be considered.

Remember arrays are very basic representations of a fixed length so they are very fast and most languages understand them depending on the type used in the array.

You need to define an array size at the time that it is created and cannot change its size later. Lists and other things can grow as needed which adds overhead with respect to memory allocation.

Lists and other types are useful because they can do a lot but sometimes you don't need all that extra overhead so an array is all you need.

It's like driving a 4x4 because you think one day you might need to go off roading even though there is 99.9% of a chance you will be on normal roads. Array would be the basic car and a List for example would be a 4x4... it does everything else a car can do (an under the hood might use most of the same parts) but at the expense of gas, cost, might not fit in certain parking stalls, etc...

Arrays = performance and compatability

Lists (or other representations) = ease of use at a cost of performance and compatability

blocks|key|1019897|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1019898|数组失去了(一些)意义吗？|blockquote|1019899|1019900|1019901|是。对于许多需要项目“表”的任务，现在有了更灵活、更有用的解决方案，如List<>和IEnumerable<>。|offset|length|style|CODE|1019902|1019903|数组已经失去了它们的重要性吗？|1019904|1019905|1019906|不是的。它们是最快的存储形式，并且在大多数集合类、System.String等“幕后”使用。|1019907|因此，数组已经变得更加低级，应用程序程序员将不再经常直接使用它们。|1019908|entityMap^0|0|0|0|0|Z|6|16|D|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|X|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Z|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|10|7|@$H|11|I|12|J|K]|$H|13|I|14|J|K]]|8|@]|9|$]]|$1|L|3|-4|4|5|6|15|7|@]|8|@]|9|$]]|$1|M|3|N|4|C|6|16|7|@]|8|@]|9|$]]|$1|O|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|18|7|@]|8|@]|9|$]]|$1|Q|3|R|4|5|6|19|7|@]|8|@]|9|$]]|$1|S|3|T|4|5|6|1A|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|1B|7|@]|8|@]|9|$]]]|V|$]]

<blockquote>
 Have arrays lost (some) significance? 
</blockquote>

Yes. For many tasks requiring a 'table' of items there now are more flexible and useful solutions like <code>List&lt;&gt;</code> and <code>IEnumerable&lt;&gt;</code>. 

<blockquote>
 Have arrays lost their importance?
</blockquote>

No. They are the fastest form of storage and they are used 'under the hood' in most of the collection classes, System.String etc. 

So, arrays have become more low-level, and an application programmer will be using them directly less often.

blocks|key|1764872|text|除此之外，您提到的许多优秀的集合类都是使用数组实现的。您可能没有显式地使用它们，但是您正在使用大量的它们，并且您的程序对此更好。这意味着数组必须在该语言中使用(或者集合是使用大量本机代码直接实现的，这会更糟糕)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1764873|entityMap^0|1Y|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Quite apart from everything else, many of those great collection classes you refer to are implemented using arrays. You might not be using them explicitly, but you're using loads of them and your program is better for it. That means that arrays must be in the language (or that the collections are implemented directly using lots of native code, which would be suckier).

blocks|key|1767452|text|是?每当我有一个在内部维护固定大小的项集合的类型时，我都会使用一个数组，因为它迭代速度最快，需要的内存也最少。如果你不需要这些特性，那么使用List<T>、Queue<T>等就没有意义了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1767453|entityMap^0|1Y|7|26|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Yes? Anytime I have a type which internally maintains a fixed-size collection of items, I use an array as it's the fastest to iterate and requires the least memory. No sense using a <code>List&lt;T&gt;</code>, <code>Queue&lt;T&gt;</code>, etc. if you don't need those features.

blocks|key|1019856|text|我每天使用数组的两种情况：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1019857|1019858|图像分析。图像几乎总是通过arrays.|unordered-list-item|1019859|External硬件进行byte[]或int[]通信。大多数设备都需要结构完美的数组来发送/接收消息。|1019860|1019861|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

Two cases where I work daily with arrays:

<ul>
<li>Image analysis. Images are almost always byte[] or int[] arrays.</li>
<li>External hardware communication. Most devices require perfectly structured arrays to send/receive messages.</li>
</ul>

blocks|key|1019744|text|这是一个合理的问题，但答案肯定是它们仍然有用。速度是一个原因，固定大小的简单性是另一个原因。但我认为最重要的是灵活性。它为您设计自己的集合提供了一个很好的基础，如果您需要的话，可以使用一个简单的数组作为后盾。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1019745|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's a fair question, but the answer is definitely that they're still useful. Speed is one reason, simplicity for fixed sizes is another. But I think the most important one is flexibility. It gives you a nice base to design your own collection, backed by a simple array, if you ever needed it.

blocks|key|1764795|text|不，数组不会失去它的重要性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1764796|当你提前知道了数据项的编号时，你可以去数组，它可以让你非常快速地访问。|1764797|2-在图论中，当你存储顶点之间的链接信息时，你可以使用比LinkList更快的数组来实现。|1764798|3-一些像string.split这样的方法返回数组。|1764799|您可以在大量的计算机问题中使用这个出色的静态项目占位符|1764800|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

No , Array will not loose its importance.

As when you know about the no of items in advance , you can go for array which gives you very fast access.

2- In Graph theroy , still when you store information about link between vertex , you can implment using arrays which are more fast than LinkList implementation.

3- Some methods like string.split returns array.

you can use this wonderful static placeholder of items in a verity of computer problems

blocks|key|1021228|text|我使用数组来操纵图像，就像在WritableBitmap类中一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1021229|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I use arrays to maniulate images like in WritableBitmap class.

blocks|key|4414489|text|有一件事我必须告诉你，数组是任何编程语言的构建块。如果你想声明一个有多个元素的存储，数组是你的基本选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4414490|比方说一个列表。|4414491|如果你看到List的定义，它实际上是|4414492|T[]项目|4414493|只需使用Reflector并找到List的定义，你会惊讶地发现List实际上是一个数组。在.NET中，除LinkedList以外的大多数集合基本上都是数组实现。他们使用Array，因为它的存储和检索速度很快。|4414494|我同意数组有更新或删除的限制，如果你主要强调的是存储而不是速度，你可能会选择链表。|4414495|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

One thing I must tell you Arrays are the building blocks for any programming language. If you want to declare a storage having more than one element, Arrays are the basic option for you.

Say for instance a List. 

If you see the definition of List, it actually holds 

T[] items

Just use Reflector and find the definition of List, you will be surprised to find out List to be actually an Array. In .NET most of the collection other than LinkedList are basically an Array implementation. They used Array because of its fast storage and retrieval.

I agree that Array has limitation of Update or Remove, if your main emphasis is in storage than speed, you might go for Linked List.

blocks|key|3004859|text|你认为那些花哨的收藏品背后的支持领域是什么？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3004860|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What do you think the backing field behind many of those fancy collections is?

For every situation that warrants the use of an array ... there is an awesome collection with benefits. Is there any specific use case for Arrays any more in .NET?

Have Arrays in .NET lost their significance?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

对于每一种需要使用数组的情况...有一个非常棒的集合，有很多好处。在.NET中，是否还有任何特定的数组用例？

问.NET中的数组已经失去了它们的意义吗？
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET中的数组已经失去了它们的意义吗？EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问.NET中的数组已经失去了它们的意义吗？
EN