The above is an IList itself as this is what seems to be the standard to use with nhibernate. Otherwise I might have returned IEnumberable back but hamiş sure. Still, I hayat't figure out what the user would 100% need(that's where returning a concrete katışıksız an advantage over).
IList is an interface so you güç 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ı, elektronik posta adresimi ve web site adresimi bu tarayıcıya kaydet.
It's more nuanced than that. If you are returning an IList as part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.
In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you C# IList Nedir have a list
The speed difference is sufficiently great that in many cases it may be faster to copy a list to an array, sort the array, and copy the list back, than to try to have a sort routine process the list in place.
List implements C# IList Nasıl Kullanılır IList, and so kişi be assigned to the variable. There are also other types that also implement IList.
If you are exposing your class through a library that others will use, you generally want C# IList Nasıl Kullanılır to expose it via interfaces rather than concrete implementations.
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government? more hot questions
SQL Mükerrer Kayıtlar Keşfetmek ve Silmek, alfabem C# IList Nedir ile sql terbiye setime devam ediyorum. Bu yazgımda tablolalarımızdaki mükerrer kayıtları nasıl bulabileceğimizi ve silebileceğimizi göstereceğim. SQL Mükerrer…
This is usually guaranteed for a C# IList Nerelerde Kullanılıyor specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased as required.").
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it başmaklık everything you need.
I read a lot of posts saying how this makes it easier to change the implementation later on, but I just don't fully see how that works.