Hakkında herşey C# IList Nerelerde Kullanılıyor

Hakkında herşey C# IList Nerelerde Kullanılıyor

Blog Article

I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method kakım well as casting to a List but none of these seemed overly elegant.

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?

If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?

Kendi koleksiyon sınıflarınızı oluştururken gene kullanılabilir kod yazmanızı sağlamlar: C# CollectionBase kullanarak genel derlem fiillemlerini bağırsakeren bir anayasa dershane oluşturabilirsiniz.

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.

This level of abstraction goes the other direction when it belongs to method parameters. When you pass your list to a method that accepts IEnumerable you can be sure that your list is not C# IList Kullanımı going to C# IList Neden Kullanmalıyız be modified. When you are the person implementing the method and you say you accept an IEnumerable because all you need to do is C# IList Nedir iterate through that list.

The cost to do this is minimal, why not save yourself the headache later? It's what the interface principle is all about.

OdedOded 496k101101 gold badges890890 silver badges1k1k bronze badges C# IList Kullanımı Add a comment  

For collections you should aim to use IEnumerable where possible. This gives the most flexibility but is not always suited.

Coming soon: Throughout 2024 we will be phasing out GitHub Issues kakım the feedback mechanism for content and replacing it with a new feedback system. For more information see: .

I know that IList is the interface and List is the concrete type but I still don't 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 there a better way to decide when to use the interface or the concrete type?

List communicates "I need to get and set the elements of this sequence in arbitrary order and I only accept lists; I do derece accept arrays."

Özel koleksiyonlar oluşturmanıza olanak tanılamar: ölçün koleksiyon sınıfları ihtiyaçlarınızı mukabillamıyorsa, kendi özel koleksiyonlarınızı C# CollectionBase kullanarak oluşturabilirsiniz. Bu, muta bünyelarınızı istediğiniz şekilde özelleştirmenizi sağlar.

There is C# IList Nerelerde Kullanılıyor a complication though that dynamic can't see explicit implementations, so something dirilik implement IList and IList-of-T and yet still be completely unusable from dynamic.