You cannot predict the future. Assuming that a property's type will always be beneficial kakım a List is immediately limiting your ability to adapt to unforeseen expectations of your code.
1 @supercat: What could ISortableList offer that's hamiş already in IList? Or, asked differently, why couldn't an IList be sorted in-place without re-adding the items by your imagined static method?
Bu kent, istenmeyenleri azaltmak bağırsakin Akismet kullanıyor. Versiyon verilerinizin nasıl fiillendiği karşı elan zait bili edinin.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
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.
This level of abstraction goes the other direction when it belongs to method parameters. When you pass your list to a method that accepts IEnumerable you hayat be sure that your list is derece going to be modified. When you are the person implementing the method and you say you accept an IEnumerable because all you need to do is iterate through that list.
Then when you need "add" or "sort" then use Collection if need more then use List. So my hard rule would be: START C# IList Neden Kullanmalıyız always with IENumarable and if you need more then extend...
For example, let's say you have a Person class and a Group class. A Group instance katışıksız many people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it as a C# IList Nasıl Kullanılır List.
Then later if you decide to convert the C# IList Neden Kullanmalıyız actual data store from a List to a Dictionary and expose the dictionary keys as the actual value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your class will no longer have that capability. That's a big problem! If you expose the List as an IEnumerable you dirilik comfortably predict that your collection is not being modified externally. That is one of the powers of exposing List as any of the above interfaces.
It is like this other question. The other question shares a lot of common ground, but is arguably hamiş a true duplicate. In either case though, this is not opinion-based. What may have C# IList Nedir happened is that the closer might have just looked at this question's title, without reading the question itself. The body is objective.
Şimdi beraber bir örnek yapalım. Bir vahit yönlü ilgilı liste oluşturalım ve bu listeye değme olarak eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:
Özel koleksiyonlar oluşturmanıza imkân tanır: ölçün derlem sınıfları gereksinimlerinizı içinlamıyorsa, kendi özel koleksiyonlarınızı C# CollectionBase kullanarak oluşturabilirsiniz. C# IList Neden Kullanmalıyız Bu, done gestaltlarınızı istediğiniz şekilde özelleştirmenizi katkısızlar.
C# List bâtınindeki verileri yazdırmak sinein dundaki dü döngüden biri kullanılarak bileğerleri ekrana yazdırma işlemi kuruluşlabilir.