It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
Your functions above only care about being able to iterate over a list. Ideally they shouldn't need to know who implements that list or how they implement it.
C# Mod Alma İşlemi , hatmız ile c sharp eğitimimize devam ediyoruz. Bu dersimizde Mod derç doğrusu bölme davranışleminden mütebaki bulma medarımaişetlemini göreceğiz. Bu konu…
Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Inside the method, you should use var, instead of IList or List. When your veri source changes to come from a method instead, your onlySomeInts method will survive.
You kişi look at this argument from several angles including the one of a purely OO approach which says to izlence C# IList Nedir against an Interface derece an implementation. With this thought, using IList follows the same principal birli passing around and using Interfaces that you define from scratch. I also C# IList Neden Kullanmalıyız 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.
If the parameter type is IList, then the caller saf much more freedom, and dirilik use classes you never heard about, which may derece even have existed when your code was written.
tranmqtranmq 15.5k33 gold badges3232 silver badges2727 bronze badges 6 But in this case I hayat't bind my collection to DataGridView rather I have to expose the _list member in MyCollection.
Do the decoupling capacitors act bey capacitive load to the opamp which is used to make a virtual gorund?
List communicates "I need to get and takım the elements of this C# IList Neden Kullanmalıyız sequence in arbitrary order and I only accept lists; I do hamiş accept arrays."
I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.
IEnumerable allows you to iterate through a collection. ICollection builds on this and also allows for adding and removing items. IList also allows for accessing and modifying them at a specific index. By exposing the one that you expect C# IList Nasıl Kullanılır your consumer to work with, you are free to change your implementation. List happens to implement all three of those interfaces. If you expose your property birli a List or even an IList when all you want your consumer to have is the ability to C# IList Kullanımı iterate through the collection. Then they could come to depend on the fact that they kişi modify the list.