Note that, if your API is only going to be used in foreach loops, etc, then you might want to consider just exposing IEnumerable instead.
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
David MillsDavid Mills 2,41511 gold badge2323 silver badges2525 bronze badges 6 2 The right approach really would have been to offer an ISortableList interface (with methods to sort a portion of the list using some particular comparer), have List implement it, and have a static method which could sort any IList by checking whether it implemented ISortableList and, if hamiş, copying it to an array, sorting that, clearing the IList, and re-adding the items.
swilliamsswilliams 48.6k2727 gold badges101101 silver badges130130 bronze badges 3 5 why hamiş make it a just a List in the first place? I still don't understand why bonus you get from making it a IList then in the constructor you make it into a List
The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base type, with no additional preconditions or postconditions.
Dizilerde olduğu gibi başta kaç pare elemanla çaldatmaışılacağı belirtilmek zorunda değildir. Dizilerde başüstüneğu kabilinden eleman ekleme, silme davranışlemleri uygulanabilir ve araya eleman eklenebilir. Rabıtlı listeler esenladığı avantajlardan dolayı henüz çok tercih edilir.
Linked List (Destelı Liste) Demetlı listeler programcılara C# IList Nerelerde Kullanılıyor çeşitli kolaylıklar katkısızlar. Katkısızladığı kolaylıklar sayesinde yaygın olarak kullanılır ve tercih edilirler. Destelı listeler, saf done bünyesına misal ancak dizilere nazaran henüz avantajlıdır.
Taking LinkedList vs taking List vs IList all communicate something of the performance guarantees required by the code being called.
On the other hand, when returning C# IList Nedir an object out of a function, you want to give the user the richest possible takım of operations without them having to cast around. So in that case, if it's a C# IList Neden Kullanmalıyız List internally, return a copy bey a List.
In this case you could pass C# IList Kullanımı in any class which implements the IList interface. If you used List instead, only a List instance could be passed in.
Unless you have a very compelling reason C# IList Nerelerde Kullanılıyor to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it has everything you need.
The other general reason for using interfaces is to expose the minimal amount of knowledge necessary to the user of an object. Consider the (contrived) case where I have a data object that implements IList.