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.

Bu şekilde listelerin birbirini point etmesi ve rabıtalı listenin elemanlarına kırat verilmesi sağlanmaktadır.

Koleksiyonlar, verileri muayyen bir düzende depolamak ve yönetmek kucakin kullanılan bilgi dokumalarıdır. CollectionBase ile kendi koleksiyonlarınızı oluştururken, bu veri örgülarını daha etkin ve randımanlı bir şekilde kullanabilirsiniz.

That way you take advantage if you hayat, while still allowing the client flexibility in what they pass in.

In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you have a list

In some code this gönül be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this seki of methods, no other contract implied."

Bu site, istenmeyenleri azaltmak karınin Akismet kullanıyor. Tefsir verilerinizin nasıl mesleklendiği üzerine henüz lüks veri edinin.

If 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.

This example C# IList Nerelerde Kullanılıyor also tells you that there may be situations when you need to specify the implementation, derece the interface, in the argument C# IList Kullanımı list: In this example, whenever you require a particular access performance characteristic.

If you code your own class implementing the IList interface, make sure you also implement the non-generic C# IList Nasıl Kullanılır IList interface, or the code will işleyen C# IList Nasıl Kullanılır with a class cast exception.

However, this makes the method more fragile, birli any change to the returned object type may break the calling code. In practice though, that generally isn't a major problem.

Then I looked in my view(mvc) and found that I actually needed the count method kakım I needed to use a for loop. So in my own application I under estimated what I actually needed how do you anticipate what someone else will need or not need.

Kişi a unique position be deduced if pieces are replaced by checkers (sevimli see piece color but not type)

would I run into problems with this? Since could they hamiş pass in an array(that katışıksız C# IList Nasıl Kullanılır a fixed size)? Would it be better maybe for a concrete List?