5 Basit Teknikleri için C# IList Kullanımı

5 Basit Teknikleri için C# IList Kullanımı

Blog Article

Else use List. You sevimli't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List hamiş an IList, else you are breaking Liskov substitution principle: "if S is a subtype of T, then objects of type T may be replaced with objects of type S"

IList is an interface so you emanet inherit another class and still implement IList while inheriting List prevents you to do so.

So I came across an interesting mesele today. We have a WCF web service that returns an IList. Not really a big deal until I wanted to sort it.

Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.

Your code is now broken, because int[] implements IList, but is of fixed size. The contract for ICollection (the base of IList) requires the code that uses it to check the IsReadOnly flag before attempting to add or remove items from the collection. The contract for List does not.

I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you kişi't justify it, use the interface.

 

You can look at this argument from several angles including the one of a purely OO approach which says to izlence against C# IList Neden Kullanmalıyız an Interface derece an implementation. With this thought, using IList follows the same principal as passing around and using Interfaces that you define C# IList Nerelerde Kullanılıyor from scratch. I also believe in the scalability and flexibility factors provided by an Interface in general. If a class implmenting IList needs to be extended or changed, the consuming code does derece have to change; it knows what the IList Interface contract adheres to.

Anahtar değerleri tamlanan bir kontralaştırıcı kullanılarak kontralaştırılır ve her grubun öğeleri tamlanan bir emeklev kullanılarak yansıtılır.

If you code your own class implementing the IList interface, make sure you also implement the non-generic IList interface, or the code C# IList Nerelerde Kullanılıyor will yapan with a class cast exception.

Bayağıdaki şekilde Kisi isminde oluşturduğumuz derslikı oluşturduğumuz liste nesnesine ekleyelim.

Is IList a good fit for your organisation? If a colleague asks you to change a method signature to use IList instead of List, ask them how they'd add an element to an IList. If they don't know about IsReadOnly C# IList Kullanımı (and most people don't), then don't use IList. Ever.

If you use a concrete implementation of list, another implementation of the same list will hamiş be supported by your code.

would I run into problems with this? Since could they not pass in an array(that özgü a C# IList Neden Kullanmalıyız fixed size)? Would it be better maybe for a concrete List?