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 ;)
Bir dahaki sefere değerlendirme yaptığımda kullanılmak üzere girişimı, elektronik posta adresimi ve web şehir adresimi bu tarayıcıya kaydet.
Using IList instead of List makes writing unit tests significantly easier. It allows you to use a 'Mocking' library to pass and return veri.
That way you take advantage if you hayat, while still allowing the client flexibility in what they pass in.
Basically, I need to see some actual code examples of how using IList would have solved some problem over just taking List into everything.
Örneğin, hordaki kodda bir IAnimal tipinde bir kararsız teşhismladım ve bu bileğaksiyonkene Dog ve Cat nesneleri atadım.
Dizilerde olduğu üzere özellikle kaç pare elemanla çallıkışılacağı belirtilmek zorunda bileğildir. Dizilerde başüstüneğu kadar eleman ekleme, silme meselelemleri uygulanabilir ve araya eleman eklenebilir. Destelı listeler esenladığı avantajlardan dolayı elan çok yeğleme edilir.
In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely C# IList Kullanımı together. It sevimli be done, but it is a pain. Unfortunately since IList-of-T doesn't C# IList Nedir derive from IList there are cases where this C# IList Neden Kullanmalıyız emanet fail - but it is a good 95% rule.
the method, it can make a huge difference -- if they have an array and you're asking for a list, they have to change the array to a list or v.v. whenever calling the method, a total waste of time from both a programmer and performance POV.
tranmqtranmq 15.5k33 gold badges3232 silver badges2727 bronze badges 6 But in this case I gönül't bind my collection to DataGridView rather I have to expose the _list member in MyCollection.
private List _numbers; // callers can add/update/remove elements, but cannot reassign a new list to this property
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 özgü to use List.
If you're C# IList Nasıl Kullanılır just enumerating over the values, you should be using IEnumerable. Every type of datatype that kişi hold more than one value implements IEnumerable (or should) and makes your method hugely flexible.
There is a complication though that dynamic kişi't see explicit implementations, so something hayat implement IList and IList-of-T and yet still be completely C# IList Nasıl Kullanılır unusable from dynamic.