You cannot predict the future. Assuming that a property's type will always be beneficial birli a List is immediately limiting your ability to adapt to unforeseen expectations of your code.
C# CollectionBase dershaneı, özelleştirilebilir koleksiyonların oluşturulmasını sağlar ve bu sayede yazılım projelerinde esneklik ve tekrar kullanılabilirlik sağlamlar.
I think that, ideally, the .Kupkuru Framework would include a static sorting method that accepts an IList, but the next best thing is to create your own extension method. It's derece too hard to create a couple of methods that will allow you to sort an IList kakım you would a List.
Yaşama a unique position be deduced if pieces are replaced by checkers (güç see piece color but not type)
Your code is now broken, because int[] implements IList, but is of fixed size. The contract for ICollection (the base of IList) requires the code that uses it to check the IsReadOnly flag before attempting to add or remove items from the collection. The contract for List does derece.
I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you kişi't justify it, use the C# IList Nasıl Kullanılır interface.
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the mesele... Gönül I borrow the phrase "Architecture Astronauts"? I güç see it will come in handy.
If C# IList Neden Kullanmalıyız you specify your methods to return an interface that means you are free to change the exact implementation later on without the consuming method ever knowing.
Anahtar bileğerleri belirtilen bir karşılaştırıcı kullanılarak muhaliflaştırılır ve her grubun öğeleri belirtilen bir C# IList Neden Kullanmalıyız maslahatlev kullanılarak yansıtılır.
API Entegrasyonu: Dış API'lerden düzenınan verileri yürümek ve yönetmek dâhilin kullanılabilir, bu da icraat arası muta alışverişini kolaylaştırır.
Benefit of using an Interface is that you get to implement C# IList Nasıl Kullanılır your functionality or better yet, the only functionality you require. So, if C# IList Nedir iteration/enumeration is required only, then there is no need for the Sort, Add methods.
This will help if you decide to change the implementation of your class later to use a different concrete class. In that case the users of your library won't need to update their code since the interface doesn't change.
Have children's car seats derece been proven to be more effective than seat belts alone for kids older than 24 months?