We needed the list indexer infrequently, so the inefficiency was derece a mesele. If it had been, we could have provided some other implementation of IList, perhaps kakım a collection of small-enough arrays, that would have been more efficiently indexable while also avoiding large objects.
Lütfen kötüdaki kutuya şikayetinizin detaylarını yazın. Şikayetinizi değerlendirildikten sonrasında size fen vereceğiz.
Elemanların Sıralı Yapkaloriı Kayırma: IList, elemanların eklenme sırasını korur. Bu özellik, done yapkaloriın sıralı olmasını ve programın beklentilerine onat çtuzakışmasını sağlar.
Kendi derme sınıflarınızı oluştururken gene kullanılabilir şifre yazmanızı sağlar: C# CollectionBase kullanarak genel derlem sorunlemlerini muhtevaeren bir asliye derslik oluşturabilirsiniz.
IList is a interface and doesn't have any implementation, so the performance of IList depending the class it implements
Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Kupkuru framework are so remote that it's theoretical jelly tots reserved for "best practices".
The cost to do this is minimal, why not save yourself the headache later? It's what the interface principle is all about.
You emanet look at this argument from several angles including the one of a purely OO approach which says to yetişek against an Interface derece an implementation. With this thought, using IList follows the same principal bey passing around and using Interfaces that you define from scratch. I also believe in the scalability and flexibility factors provided by an Interface in general. If a class implmenting C# IList Nedir IList needs to be extended or changed, the consuming code does hamiş have to change; it knows what the IList Interface contract adheres to.
In most cases, if you are using a List and you think you could use a narrower interface instead - why hamiş IEnumerable? This is often a better fit if you don't need to add items. If you need to add to the collection, use the concrete type, List.
Then later if you decide to convert the actual C# IList Nedir data store from a List to a Dictionary and expose the dictionary keys kakım the actual value for the property (I have had to do exactly this before). Then consumers C# IList Kullanımı who have come to expect that their changes will be reflected inside of your class will no longer have that C# IList Nasıl Kullanılır capability. That's a big sorun! If you expose the List kakım an IEnumerable you dirilik comfortably predict that your collection is not being modified externally. That is one of the C# IList Nedir powers of exposing List birli any of the above interfaces.
IList is not a class; it's an interface that classes gönül implement. The interface itself is just a contract between the consumer of the class and the class itself. This line of code will work:
The most important case for using interfaces over implementations is in the parameters to your API. If your API takes a List parameter, then anyone who uses it başmaklık to use List.
for your return types. This gives your callers the most flexibility in passing in types to your methods and the most opportunities to cast/reuse the return values.
Encapsulation relies on telling clients bey little about the implementation of your class as possible. If you return a concrete List, you can't then change to some other better type without forcing all of your clients to re-compile/update.