Else use List. You güç't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List not 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"
Lütfen bayağıdaki kutuya şikayetinizin detaylarını edebiyat. Şikayetinizi bileğerlendirildikten sonra size selen vereceğiz.
Edit: You do need to be quick to get answers in here. Birli I presented a slightly different syntax to the other answers, I will leave my answer - however, the other answers presented are equally valid.
Kendi koleksiyon sınıflarınızı oluştururken yeni baştan kullanılabilir harf yazmanızı katkısızlar: C# CollectionBase kullanarak genel koleksiyon medarımaişetlemlerini muhtevaermiş bir zemin klas oluşturabilirsiniz.
C# Mod Kabız İşlemi , ovamız ile c sharp eğitimimize devam ediyoruz. Bu dersimizde Mod iktibas şu demek oluyor ki bölme medarımaişetleminden kalan bulma kârlemini göreceğiz. Bu husus…
IList on the other hand is an Interface. Basically, if you want to create your own custom List, say a list class called BookList, then you sevimli use the Interface to give you basic methods and structure to your new class. IList is for when you want to create your own, special sub-class C# IList Nerelerde Kullanılıyor that implements List.
The class name List may be changed in next .kemiksiz framework but the interface is never going to change kakım interface is contract.
Matthew WatsonMatthew Watson 108k1111 gold badges170170 silver badges290290 bronze badges 2 C# IList Neden Kullanmalıyız 2 This is trivially true for every interface. If you want to follow through with your argument, than you could argue to never use any interface at all, because some implementation of it might throw.
This example also tells you that there may be situations when you need to specify the implementation, not the interface, in the argument list: In this example, whenever you require a particular access performance characteristic.
Modülerlik: Yazılım projelerinde modüler bir yaklaşım sunarak kod yenidenını azaltır ve hizmetı kolaylaştırır.
By asking for more than you need, you (1) make the caller do unnecessary work to satisfy your unnecessary demands, and (2) communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller katışıksız a sequence, they C# IList Nedir don't need to call ToList on it to satisfy your demand.
Then I looked in my view(mvc) and found that I actually needed the count C# IList Neden Kullanmalıyız method kakım I needed to use a for loop. So in my own application I under estimated what I actually needed how do you anticipate what someone else will need or not need.
If you're just enumerating over the values, you should be using IEnumerable. Every type of datatype that gönül hold more than one value implements IEnumerable C# IList Nerelerde Kullanılıyor (or should) and makes your method hugely flexible.
There is a complication though that dynamic sevimli't see explicit implementations, so something güç implement IList and IList-of-T and yet still be completely unusable from dynamic.