driisdriis 163k4545 gold badges268268 silver badges343343 bronze badges 3 Sorry, but even now there are plenty of uses for library code to use IList (non-generic). Anyone who says otherwise hasn't suffered enough reflection / veri-binding / etc ;)
IList is an interface so you can inherit another class and still implement IList while inheriting List prevents you to do so.
Bir dahaki sefere versiyon yaptığımda kullanılmak üzere kademı, e-posta adresimi ve web kent adresimi bu tarayıcıevet kaydet.
The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list.
This will allow me to do generic processing on almost any array in the .NET framework, unless it uses IEnumerable and not IList, which happens sometimes.
List is a specific implementation of IList, which is a container that hayat be addressed the same way kakım a linear array T[] using an integer index. When you specify IList as 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.
The cost to do this is minimal, why hamiş save yourself the headache later? It's what the interface principle is C# IList Neden Kullanmalıyız all about.
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.
In most cases, if you are using a List and you think you could use a narrower interface instead - why hamiş IEnumerable? This is often a better fit if you don't need to add items. If you need to add to the collection, use the concrete type, List.
API Entegrasyonu: Dış API'lerden alınan verileri gitmek ve yönetmek karınin kullanılabilir, bu da uygulamalar arası muta alışverişini kolaylaştırır.
Gönül you please provide me some link to a class that implements IList interface or C# IList Nasıl Kullanılır provide me a code that at least implements Add and Remove methods?
rajeshrajesh 39133 silver badges22 bronze badges 1 8 Excellent, clear answer, which I marked bey helpful. However, I would add that for C# IList Nasıl Kullanılır most developers, most of the time, the tiny difference in program size and performance is not worth C# IList Nasıl Kullanılır worrying about: if in doubt, just use a List.
This will help if you decide to change the implementation of your class later to use a different concrete class. In that case the users of C# IList Neden Kullanmalıyız your library won't need to update their code since the interface doesn't change.
would I run into problems with this? Since could they hamiş pass in an array(that katışıksız a fixed size)? Would it be better maybe for a concrete List?