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 / data-binding / etc ;)
Başarım Optimizasyonu: IList, data erişimini optimize ederek uygulamanın performansını fazlalıkrabilir ve akıl yönetimini iyileştirebilir.
Say I have a function that returns IEnumerable, inside the function I may use a List for an internal backing store to generate my collection, but I only want callers to enumerate it's contents, not add or remove. Accepting an interface birli a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change it."
The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list.
In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you have a list
so its safety for you and freedom to C# IList Nerelerde Kullanılıyor the coder who is writing concrete implementation to change or add more functionality to his concrete class.
class Kisi string ad; string soyad; public string Ad C# IList Kullanımı get return ad; takım ad = value; public string Soyad get return soyad; kaş soyad = value;
Bir dahaki C# IList Nedir sefere değerlendirme yaptığımda kullanılmak üzere adımı, elektronik posta adresimi ve web site adresimi bu tarayıcıevet kaydet.
Taking LinkedList vs taking List vs IList all communicate something of the performance guarantees required by the code being called.
kemiller2002kemiller2002 115k2828 gold badges198198 C# IList Kullanımı silver badges253253 bronze badges Add a comment
The most important case for using interfaces over implementations is in the parameters to your API. If your API takes a List parameter, then anyone who uses it başmaklık to use List.
I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.
ahead of time. Data-binding is a classic example here; C# IList Nerelerde Kullanılıyor a DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what properties are available. It birey't use generics in this case.