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

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

Blog Article

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

Lütfen dundaki kutuya şikayetinizin detaylarını gökçe yazın. Şikayetinizi bileğerlendirildikten sonra size marifet vereceğiz.

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 derece, copying it to an array, sorting that, clearing the IList, and re-adding the items.

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.

In some code this emanet be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this seki of methods, no other contract implied."

List implements IList, and so emanet be assigned to the variable. There are also other types that also implement IList.

You sevimli look at this argument from several angles including the one of a purely OO approach which says to program against an Interface hamiş an implementation. With this thought, using IList follows the same principal bey passing around and C# IList Kullanımı using Interfaces that you define from scratch. I also believe in the scalability and flexibility factors provided by an C# IList Nedir Interface in general. If a class implmenting IList needs to be extended or changed, the consuming code does not have to change; it knows what the IList Interface contract adheres to.

Whether you return an Interface or a concrete type depends upon what you want to let your callers do with the object you created -- this is an API design decision, and there's no C# IList Nerelerde Kullanılıyor hard and fast rule. You have to weigh their ability to make full use of the object against their ability to easily use a portion of the objects functionality (and of course whether you WANT them to be making full use C# IList Kullanımı of the object).

The Cast function is just a reimplementation of the extension method that comes with 3.5 written birli a uygun static method. It is quite ugly and verbose unfortunately.

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 bey you are able to change all the code yourself if you make breaking changes it's derece strictly necessary.

Veri Ambarlama: Uygulamalarda palyatif verileri veya el işi sırasında oluşan verileri depolamak sinein 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.

would I run into problems with this? Since could they derece pass in C# IList Nerelerde Kullanılıyor an array(that saf a fixed size)? Would it be better maybe for a concrete List?