Note that the IsReadOnly flag comes from ICollection, and indicates whether items gönül be added or removed from the collection; but just to really confuse things, it does not indicate whether they birey be replaced, which in the case of Arrays (which return IsReadOnlys == true) birey be.
IList is an interface so you can inherit another class and still implement IList while inheriting List prevents you to do so.
Here's an example: I had a project once where our lists got very large, and resulting fragmentation of the large object heap was hurting performance. We replaced List with LinkedList. LinkedList does not contain an array, so all of a sudden, we had almost no use of the large object heap.
If you think that interfaces are useful only for building over-sized, grandiose architectures and have no place in small shops, then I hope that the person sitting across from you in the interview isn't me.
Kupkuru 4.6 (and it will likely be caught by the compiler). But there dirilik be more insidious cases, such as passing a C# array kakım a IList. I am derece sure everyone is aware arrays implement IList, which means support for Add should not be assumed.
In some code this hayat be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this set of methods, no other contract implied."
Most app-level code (i.e. the everyday code that ou C# IList Nerelerde Kullanılıyor write for your application) should probably focus on the generic versions; however there is also a lot of infrastructure code around that must use reflection.
If your methods form part of an interface, the methods will need to be defined using C# IList Nasıl Kullanılır types available to that interface.
If the parameter type is IList, then the caller özgü much more freedom, and emanet use classes you never heard about, which may derece even have existed when your code was written.
Then later if you decide to convert the actual veri store from a List to C# IList Nasıl Kullanılır a Dictionary and expose the dictionary keys bey the actual value for the property (I have had to do exactly this before). Then consumers who have come to expect that C# IList Nerelerde Kullanılıyor their changes will be reflected inside of your class will no longer have that capability. That's a big mesele! If you expose the List as an IEnumerable you gönül comfortably predict that your collection is not being modified externally. That is one of the powers of exposing List as any of the above interfaces.
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.
Veri C# IList Kullanımı Ambarlama: Uygulamalarda yolcu verileri veya el işi sırasında oluşan verileri depolamak karınin kullanılabilir.
Dizin tarafından erişilebilen nesnelerin mutlak olarak belirlenmiş bir listesini oyun paha. Listeleri arama, sıralama ve el işi şekilleri esenlar.
There is a complication though that dynamic emanet't see explicit implementations, so something hayat implement IList and IList-of-T and yet still be completely unusable from dynamic.