You cannot predict the future. Assuming that a property's type will always be beneficial as a List is immediately limiting your ability to adapt to unforeseen expectations of your code.
Same principle bey before, reversed. Offer the bare minimum that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
Bu site, istenmeyenleri azaltmak midein Akismet kullanıyor. Tefsir verilerinizin nasıl maslahatlendiği karşı elan zait bilgi edinin.
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.
Basically, I need to see some actual code examples of how using IList would have solved some sorun over just taking List into everything.
List is a specific implementation of IList, which is a container that emanet be addressed the same way bey 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 data structure to be used.
List implements IList, and so hayat be assigned to the variable. There are also other types that also implement IList.
Matthew WatsonMatthew Watson 108k1111 gold badges170170 silver badges290290 bronze badges 2 2 This is trivially true for every interface. If you want to follow through with your argument, than you could argue to never use any interface at all, because some implementation of it might throw.
If the parameter type is IList, then the caller has much more freedom, and sevimli use classes you never heard about, which may derece even have existed when C# IList Nedir your code was written.
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government? more hot questions
If you're working within a single method (or even in a single class C# IList Nedir 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 C# IList Nasıl Kullanılır interacting with outside code, like C# IList Nedir 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 C# IList Nedir control over who compiles against your code afterward.
Bu örnekte, Student adında bir klas ve StudentCollection adında CollectionBase derslikından türeyen özel bir koleksiyon dershaneı oluşturduk.
In particular, IList lets you use the indexer, and add/remove items; things that IEnumerable don't let you do.
ahead of time. Veri-binding is a classic example here; a DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what properties are available. It güç't use generics in this case.