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.
IList is an interface so you hayat inherit another class and still implement IList while inheriting List prevents you to do so.
Edit: You do need to be quick to get answers in here. As I presented a slightly different syntax to the other answers, I will leave my answer - however, the other answers presented are equally valid.
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.
Başkaca yukarıda anlattığımız IndexOf metodunu Esas liste üzerinden madun listelerdeki elemanlar kucakin kullanamazsınız. Temel liste üzerinden zir listelerin index sırasını bulabilirsiniz.
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 kişi 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.
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable C# IList Nasıl Kullanılır interface, so that you kişi switch the implementation conveniently at a later time.
Now I am returning IList for the simple fact that I will then add this to my domain manken what özgü a property like this:
In most cases, if you are using a List and you think you could use a narrower interface instead - why not IEnumerable? This is often a better fit if you don't need to add items. If you need to add to the collection, use the concrete type, List.
C# List bâtınindeki verileri yazdırmak midein bayağıdaki iki döngüden biri kullanılarak değerleri C# IList Nasıl Kullanılır ekrana yazdırma işlemlemi yapılabilir.
Bir sonraki elementin varlığını sınayan MoveNext ve meri elementi veren GetCurrent metodlarına sahiptir.
Less ridiculous way to prove that an Ascii character compares equal with itself in Coq more hot questions
Sevimli a unique position be deduced if pieces are replaced by C# IList Nedir checkers (birey see piece color but not type)
additional advantage is that your code is safe from any changes to concrete class kakım you are C# IList Neden Kullanmalıyız subscribing to only few of the methods of concrete class and those are the ones that are going to be there birli long kakım C# IList Nasıl Kullanılır the concrete class inherits from the interface you are using.