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.
1 @supercat: What could ISortableList offer that's derece 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?
Diyelim ki formunuzdaki textboxları listenize doldurdunuz yalnızca Text’i boş olan textboxları bulmanız gerekiyor. Bunun midein List u kullanmanız gerekir. Mafevkda anlattığımız örneği cılız olarak yapacak olursak;
A List object allows you to create a list, add things to it, remove it, update it, index into it and etc. List is used whenever you just want a generic list where you specify object type in it and that's it.
ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't you just have to change that to the new type as well? So maybe IList to IList?
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 birey be sure that your list is hamiş 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.
You may derece ever need that option, but it's an argument. C# IList Nerelerde Kullanılıyor I think it's the entire argument for returning the interface instead of the concrete type. It's worth mentioning, but in this case it katışıksız a serious flaw.
OdedOded 496k101101 gold badges890890 silver badges1k1k bronze badges Add a comment
The idea is that you hide the implementation details from the user, and instead provide them with a stable C# IList Nedir interface. This is to reduce dependency on details that might change in the future.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: .
I know that IList is the interface and List is the concrete type but I still don't know when to use each one. What I'm doing now is if I don't need the Sort or FindAll methods I use the interface. Am I right? Is there a better way to decide when to use the interface or the concrete type?
Şimdi bu arada bir örnek yapalım. Bir tek yönlü bentlı liste oluşturalım ve bu listeye ölçüsüz olarak eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:
This C# IList Nedir will help if you decide to change the implementation of your class later to use a different concrete class. In that C# IList Nedir case the users of your library won't need to update their code since the interface doesn't change.
If you had used IList in the rest of the app you could extend List with your own custom class and C# IList Nasıl Kullanılır still be able to pass that around without refactoring.