We needed the list indexer infrequently, so the inefficiency was derece a sorun. If it had been, we could have provided some other implementation of IList, perhaps as a collection of small-enough arrays, that would have been more efficiently indexable while also avoiding large objects.
Arec BarrwinArec Barrwin 61.8k99 gold badges3030 silver badges2525 bronze badges 14 71 I have to disagree with your sardonic answer. I don't totally disagree with the sentiment of over-architecture being a real sıkıntı. However I think that especially in the case of collections that interfaces really shine.
You pass the interface so that no matter what concrete implementation of that interface you use, your code will support it.
David MillsDavid Mills 2,41511 gold badge2323 silver badges2525 bronze badges 6 2 The right approach really would have been to offer an ISortableList interface (with methods to sort a portion of the list using some particular comparer), have List implement it, and have a static method which could sort any IList by checking whether it implemented ISortableList and, if hamiş, copying it to an array, sorting that, clearing the IList, and re-adding the items.
C# Mod Alma İşlemi , yazgımız ile c sharp eğitimimize devam ediyoruz. Bu dersimizde Mod ittihaz kısaca bölme çalışmaleminden mütebaki bulma davranışlemini göreceğiz. Bu bahis…
GitHub'da bizimle ortaklık strüktürn Bu içeriğin kaynağı GitHub'da bulunabilir; burada başkaca sorunları ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Daha zait bilim muhtevain katkıda mevcut kılavuzumuzu inceleyin.
Bu şehir, istenmeyenleri azaltmak bâtınin Akismet kullanıyor. Değerlendirme verilerinizin nasıl aksiyonlendiği üzerine daha bir tomar veri edinin.
3 @phoog: Considering where Eric is coming from, it wouldn't be surprising C# IList Nasıl Kullanılır he is more cautious about breaking changes. But it is definitely a valid point.
Whether you return an Interface or a concrete type depends upon what you want to let your callers do with C# IList Nasıl Kullanılır the object you created -- this is an API design decision, and there's no hard and fast rule. You have to weigh their ability to make full use of the object against C# IList Nerelerde Kullanılıyor their ability to easily use a portion of the objects functionality (and of course whether you WANT them to be making full use of the object).
It really comes down to the kind C# IList Nerelerde Kullanılıyor 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 as a list.
Of course that only need apply to methods that are externally visible (i.e. public methods). I personally use interfaces even in internal code, but as you are able to change all the code yourself if you make breaking changes it's not strictly necessary.
Muta Depolama: Uygulamalarda arızi verileri yahut işleme sırasında oluşan verileri depolamak ciğerin kullanılabilir.
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.
For instance, if you return an IEnumerable, then you are limiting them to iterating -- they emanet't add or remove items from your object, they emanet only act against the objects. If you need to expose a C# IList Nedir 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.