Else use List. You hayat'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"

What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government?

Bu kent, istenmeyenleri azaltmak sinein Akismet kullanıyor. Versiyon verilerinizin nasıl konulendiği için daha bir küme haber edinin.

So when writing a function or method that takes a collection, write it not to take a List, but an IList, an ICollection, or IEnumerable. The generic interfaces will still work even for heterogenous lists because System.

This will allow me to do generic processing on almost any array in the .Kupkuru framework, unless it uses IEnumerable and hamiş IList, which happens sometimes.

IList on the other hand is an Interface. Basically, if you want to create your own custom List, say a list class called BookList, then you kişi use the Interface to give you basic methods and structure to your new class. IList is for when you want to create your own, special sub-class that implements List.

You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you yaşama switch the implementation conveniently at a later time.

Don't you know C# IList Kullanımı in advance if your method needs a list that hayat take additional members; don't you specify that in the method signature? What exactly were you going to do if you were passed a read only list like int[]?

For example, let's say you have a Person class and a Group class. A Group instance başmaklık many people, so a List here would make sense. C# IList Kullanımı When I declare the list object in Group I will use an IList and instantiate it bey a List.

API Entegrasyonu: Dış API'lerden allıkınan verileri yürümek ve yönetmek muhtevain kullanılabilir, bu da icraat arası data pazarini kolaylaştırır.

It is like this other question. The other question shares a lot of common ground, but is arguably derece a true duplicate. In either case though, this is derece opinion-based. What may have happened is that the closer might have just looked at this question's title, without reading the question itself. The body is objective.

The most important case for using interfaces over implementations is in the parameters to your API. If your API takes a List C# IList Nasıl Kullanılır parameter, then anyone who uses it başmaklık to use List.

In particular, IList lets you use the indexer, and add/remove items; things that IEnumerable don't let you do.

additional advantage is that your code is safe from any changes to concrete class bey you are subscribing to only few of the methods of concrete class and those are C# IList Kullanımı the ones that are going to be there birli long kakım the concrete class inherits from the interface C# IList Neden Kullanmalıyız you are using.