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 ;)

What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government?

Bir dahaki sefere versiyon yapmış olduğumda kullanılmak üzere girişimı, elektronik posta adresimi ve web kent adresimi bu tarayıcıya kaydet.

Dirilik a unique position be deduced if pieces are replaced by checkers (birey see piece color but derece type)

Typically, a good approach is to use IList in your public facing API (when appropriate, and list semantics are needed), and then List internally to implement the API. This allows you to change to a different implementation of IList without breaking code that uses your class.

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.

GitHub'da bizimle işbirliği binan Bu dâhilğin kaynağı GitHub'da bulunabilir; burada hassaten sorunları ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Henüz lüks bilim için ulamada mevcut kılavuzumuzu inceleyin.

If your methods form part of an interface, the methods will need to be defined C# IList Nasıl Kullanılır using types available to that interface.

If the parameter type is IList, then the caller başmaklık much more freedom, and güç use classes you never heard about, which may not even have existed when your code was written.

It really comes down to the kind of functionality you need. I'd suggest using the List class in most cases. IList is best for when you need to make a custom array C# IList Nasıl Kullanılır that could have some very specific rules that you'd like to encapsulate within a collection so you don't repeat yourself, but still want .NET to recognize it bey a list.

I know that IList is the interface and List is the concrete type but I still don't C# IList Nasıl Kullanılır know when to use each one. What I'm doing now is if I don't need the Sort or FindAll methods I use the interface. Am I right? Is C# IList Nerelerde Kullanılıyor there a better way to decide when to use the interface or the concrete type?

This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased kakım required.").

Dizin tarafından erişilebilen nesnelerin kesin C# IList Nasıl Kullanılır olarak belirlenmiş bir listesini simgeleme fiyat. Listeleri arama, sıralama ve el işi yöntemleri esenlar.

For instance, if you return an IEnumerable, then you are limiting them to iterating -- they dirilik't add or remove items from your object, they emanet only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.