It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.
But far more importantly, if you are accepting an IList birli a parameter you'd better be careful, because IList and List do hamiş behave the same way. Despite the similarity in name, and despite sharing an interface
Diyelim ki formunuzdaki textboxları listenize doldurdunuz sadece Text’i boş olan textboxları bulmanız gerekiyor. Bunun midein List u kullanmanız gerekir. Yukarıda anlattığımız örneği kıytırık olarak yapacak olursak;
Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.
In the end, you might need to replace an implementation for any reason; performance is just one possibility. Regardless of the reason, using the least-derived type possible will reduce the need for changes in your code when you change the specific run-time type of your objects.
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 dirilik use the Interface to give you basic C# IList Nasıl Kullanılır methods and structure to your new class. IList is for when you want to create your own, special sub-class that implements List.
Most app-level code (i.e. the everyday code that ou 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.
Don't you know in advance if your method needs a list that gönül take C# IList Nedir additional members; don't you C# IList Nerelerde Kullanılıyor specify that in the method signature? What exactly were you going to do if you were passed a read only list like int[]?
In most cases, if you are using a List and you think you could use a narrower interface instead - why not 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.
If you code your own class implementing the IList interface, make sure you also implement the non-generic IList C# IList Nedir interface, or the code will işleyen with a class cast exception.
Obviously if you are being asked which you use in an interview, you say IList, smile, and both look pleased at yourselves for being so clever. Or for a public facing API, IList. Hopefully you get my point.
Data Ambarlama: Uygulamalarda sâri verileri yahut el işi esnasında oluşan verileri depolamak karınin kullanılabilir.
List sınıfı teşhismlanırken T tip değustalıkkenini tuzakır. Doğrusu listenin içeriğinde hangi türden nesne yada bileğnöbetkenlerin olacağını belirler.
Have children's car seats not C# IList Nasıl Kullanılır been proven to be more effective than seat belts alone for kids older than 24 months?