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 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"
Lütfen adidaki kutuya şikayetinizin detaylarını edebiyat. Şikayetinizi bileğerlendirildikten sonra size vukuf vereceğiz.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list.
I tend to follow Jeffrey's advice for internal code, but for a public library, I would probably be more inclined to follow Eric's.
Convert your IList into List or some other generic collection and then you hayat easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)
The cost to C# IList Nedir do this is minimal, why not save yourself the headache later? It's what the interface principle is all about.
If you specify your methods to return an interface that means you are free to change the exact implementation later on without the consuming method ever knowing.
If you started with a concrete type and you decided to change to another one, even if it uses the same interface, you're going C# IList Neden Kullanmalıyız to break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer C# IList Nasıl Kullanılır Follow
Want to improve this question? Update the question so it kişi be answered with C# IList Kullanımı facts and citations by editing this post.
Bir ahir elementin varlığını sınayan MoveNext ve meri elementi veren GetCurrent metodlarına sahiptir.
Brad LeachBrad Leach 17k1818 gold badges7373 silver badges8888 bronze badges 1 3 It will create a new enumerable, which may not be desirable in some scenarios. You cannot sort an IList in-place through the interface except by using ArrayList.Adapter method C# IList Kullanımı in my knowledge.
If you use the concrete type all callers need to be updated. If exposed kakım IList the caller doesn't have to be changed.
I read a lot of posts saying how this makes it easier to change the implementation later on, but I just don't fully see how that works.