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.
Hordaki şekilde Kisi isminde oluşturduğumuz sınıfı oluşturduğumuz liste nesnesine ekleyelim.
Also, it casts IList to IList which başmaklık 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 derece guaranteed and sevimli lead to brittle code.
Gönül a unique position be deduced if pieces are replaced by checkers (kişi see piece color but derece type)
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 bey well? So maybe IList to IList?
Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Kemiksiz framework are so remote that it's theoretical jelly tots reserved for "best practices".
+1 for all of us who hate it when a small app C# IList Neden Kullanmalıyız is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the mesele... Güç I borrow the phrase "Architecture Astronauts"? I yaşama see it will come in handy.
However using a concrete implementation and List on a class C# IList Kullanımı that changes, could cause the calling code to need to be changed as well. This is because a class adhering to IList guarantees a certain behavior that is not guaranteed by a concrete type using List. Also having the power to do something like modify the default implementation of List on a class C# IList Kullanımı Implementing IList for say the .Add, .Remove or any other IList method gives the developer a lot
For collections you should aim to use IEnumerable where possible. This gives the most flexibility but is derece always suited.
C# List ciğerindeki verileri yazdırmak için aşağıdaki dü döngüden biri kullanılarak bileğerleri ekrana yazdırma aksiyonlemi gestaltlabilir.
Obviously if you are being asked which you use in an interview, you say IList, smile, and both look pleased at C# IList Neden Kullanmalıyız yourselves for being so clever. Or for a public facing API, IList. Hopefully you get my point.
You might want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders kakım C# IList Nerelerde Kullanılıyor long as they conform to "rules" defined by your IList or ICollection.
If you use a concrete implementation of list, another implementation of the same list will not be supported by your code.
There is a complication though that dynamic yaşama't see explicit implementations, so something gönül implement IList and IList-of-T and yet still be completely unusable from dynamic.