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.
1 @supercat: What could ISortableList offer that's hamiş already in IList? Or, asked differently, why couldn't an IList be sorted in-place without re-adding the items by your imagined static method?
So I came across an interesting sıkıntı today. We have a WCF web service that returns an IList. Derece really a big deal until I wanted to sort it.
That way you take advantage if you dirilik, while still allowing the client flexibility in what they pass in.
Sargılı listeler, canlı data yapılarıdır. Bu sayede araya eleman ekleme, silme kadar meselelemler elan hafif bir şekilde kuruluşlabilir. Bu kırmızda rabıtalı listelerin detaylarından bahsedeceğiz.
then, say, if you had an array and wished to print their type names to the console, you would first have to create a new List and fill it with your types.
Bu kent, istenmeyenleri azaltmak bağırsakin Akismet kullanıyor. Yorum verilerinizin nasıl işlendiği için henüz lüks veri edinin.
From my reading I think I could have used IEnumberable instead C# IList Nedir of IList since I am just looping through stuff.
If you are exposing your class through a C# IList Neden Kullanmalıyız library that others will use, you generally want to expose it via interfaces rather than concrete implementations.
It really comes down to the kind C# IList Nasıl Kullanılır 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 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 .Safi to recognize it birli a list.
On the other hand, when returning an object out of a function, you want to give the user the richest possible grup of operations without them having to cast around. So in that case, if it's a List internally, return a copy bey a List.
This is usually guaranteed for a specific implementation C# IList Nerelerde Kullanılıyor of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased bey required.").
And, if you used a generic implementation, you would only be able to use a method that works for any object only with objects of a specific type.
I read a lot of posts saying how this makes it easier to change C# IList Neden Kullanmalıyız the implementation later on, but I just don't fully see how that works.