Else use List. You kişi'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"
Arec BarrwinArec Barrwin 61.8k99 gold badges3030 silver badges2525 bronze badges 14 71 I have to disagree with your sardonic answer. I don't totally disagree with the sentiment of over-architecture being a real mesele. However I think that especially in the case of collections that interfaces really shine.
Also, it casts IList to IList which özgü the potential to be dangerous. In most cases that I have seen, List which implements IList is used behind the scenes to implement IList, but this is not guaranteed and gönül lead to brittle code.
Sıfır zir sonına malik tek boyutlu diziler kendiliğinden olarak uygular IList. Bu, diziler ve sair koleksiyon türleri beyninde yineleme uygulamak yürekin aynı kodu kullanabilen genel yöntemler oluşturmanıza imkân tanır.
C# Mod Kabız İşlemi , tasarmız ile c sharp eğitimimize devam ediyoruz. Bu dersimizde Mod kabız doğrusu bölme meslekleminden artan bulma meselelemini göreceğiz. Bu laf…
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList none of the C# IList Nerelerde Kullanılıyor people that used the library had to change their code.
Now I am returning IList for the simple fact that I will then add this to my domain manken what saf a property like this:
And, if you don't even need everything in IList you emanet always use IEnumerable too. With çağdaş compilers and processors, I don't think there is really any speed difference, so this is more just a matter of style.
tranmqtranmq 15.5k33 gold badges3232 silver badges2727 bronze badges 6 But in this case I C# IList Nedir yaşama't bind my collection to DataGridView rather I have to expose the _list member in MyCollection.
If you're working within a single method (or even in a single class or assembly in some cases) and no one outside is going to see what you're doing, use the fullness of a List. But if C# IList Neden Kullanmalıyız you're interacting with outside code, like when you're returning a list from a method, then you only want to declare the interface without necessarily tying yourself to a specific implementation, C# IList Nerelerde Kullanılıyor especially C# IList Nasıl Kullanılır if you have no control over who compiles against your code afterward.
Şimdi beraber bir örnek yapalım. Bir sessiz yönlü rabıtlı liste oluşturalım ve bu listeye değme olarak eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:
So typically, your methods should accept and return interfaces for collections. This leaves your own implementation and your callers room to decide on the actual implementation birli required.
For instance, if you return an IEnumerable, then you are limiting them to iterating -- they gönül't add or remove items from your object, they birey only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.