Note that the IsReadOnly flag comes from ICollection, and indicates whether items can be added or removed from the collection; but just to really confuse things, it does hamiş indicate whether they yaşama be replaced, which in the case of Arrays (which return IsReadOnlys == true) can be.
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
Bu şehir, istenmeyenleri azaltmak bağırsakin Akismet kullanıyor. Yorum verilerinizin nasıl işlendiği üzerine elan bir tomar marifet edinin.
The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list.
The accepted answer by @DavidMills is quite good, but I think it yaşama be improved upon. For one, there is no need to define the ComparisonComparer class when the framework already includes a static method Comparer.Create(Comparison). This method dirilik be used to create an IComparison on the fly.
List is a specific implementation of IList, which is a container that sevimli be addressed the same way as a linear array T[] using an integer index. When you specify IList bey the type of the method's argument, you only specify that you need certain capabilities of the container. For example, the interface specification does derece enforce a specific veri structure to be used.
Remove Silinmesini matlup kıymeti siler. Silinecek boy bos liste zarfında ansızın aşkın olması yerinde ilk kıymeti kaldırır. Bu metodu çoklukla referans tipler ile kadir çıkarmak bâtınin kullanılır. Ancak fehamet tipleri ile de kullanılabilir.
OdedOded 496k101101 gold badges890890 C# IList Neden Kullanmalıyız silver badges1k1k bronze badges Add a comment
Whether you return an Interface or a concrete type depends upon what you want to let your callers do with the object you created -- this C# IList Kullanımı is an API design decision, and there's no hard and fast rule. You have to weigh their ability to make full use C# IList Nerelerde Kullanılıyor of the object against their ability to easily use a portion of the objects functionality (and of course whether you WANT them to be making full use of the object).
List implements those büyük C# IList Nerelerde Kullanılıyor anne methods (hamiş including extension methods), on bütünüyle of that it özgü about 41 public methods, which weighs in your consideration of which one to use in your application.
If you're working within a single method (or even in a single class or assembly in some cases) and no one outside is going to see what you're doing, use the fullness of a List. But if you're interacting with outside code, like when you're returning a list from a method, then you only want to declare the interface without necessarily tying yourself to a specific implementation, especially if you have no control over who compiles against your code afterward.
List communicates "I need to get and grup the elements of this sequence in arbitrary order and I only accept lists; I do derece accept arrays."
I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.
IEnumerable allows you to iterate through a collection. ICollection builds on this and also allows for adding and removing items. IList C# IList Nerelerde Kullanılıyor also allows for accessing and modifying them at a specific index. By exposing the one that you expect your consumer to work with, you are free to change your implementation. List happens to implement all three of those interfaces. If you expose your property as a List or even an IList when all you want your consumer to have is the ability to iterate through the collection. Then they could come to depend on the fact that they yaşama modify the list.