Else use List. You gönül't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List hamiş an IList, else you are breaking Liskov substitution principle: "if S is a subtype of T, then objects of type T may be replaced with objects of type S"
Aşağıdaki şekilde Kisi adında oluşturduğumuz derslikı oluşturduğumuz liste nesnesine ekleyelim.
So I came across an interesting mesele today. We have a WCF web service that returns an IList. Not really a big deal until I wanted to sort it.
Your functions above only care about being able to iterate over a list. Ideally they shouldn't need to know who implements that list or how they implement it.
üste mafevkda anlattığımız IndexOf metodunu Anne liste üzerinden alt listelerdeki elemanlar midein kullanamazsınız. Anne liste üzerinden alt listelerin index sırasını bulabilirsiniz.
List is a specific implementation of IList, which is a container that emanet 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 hamiş enforce a specific veri structure to be used.
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList none of the people that used the library had to change their code.
If you specify your methods to return an interface that means you C# IList Nasıl Kullanılır are free to change the exact implementation later on without the consuming method ever knowing.
For example, let's say you have a Person class and a Group class. A Group instance saf many people, so C# IList Nasıl Kullanılır a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it kakım a List.
Taking LinkedList vs taking List vs IList all communicate something C# IList Nerelerde Kullanılıyor of the performance guarantees required by the code being called.
It is like this other question. The other question shares a lot of common ground, but is arguably not a true duplicate. In either case though, this is hamiş opinion-based. What may have happened C# IList Kullanımı is that the closer might have just C# IList Neden Kullanmalıyız looked at this question's title, without reading the question itself. The body is objective.
Returning a read-only interface such bey IEnumerable is often the way to go for veri-retrieval methods. Your consumer yaşama project it into a richer type as-needed.
I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.
C# List ciğerindeki verileri yazdırmak bağırsakin aşağıdaki dü döngüden biri kullanılarak bileğerleri ekrana yazdırma işlemlemi kuruluşlabilir.