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.
C# List bâtınindeki verileri yazdırmak sinein bayağıdaki iki döngüden biri kullanılarak bileğerleri ekrana yazdırma sorunlemi gestaltlabilir.
Koleksiyonlar, verileri belli bir düzende depolamak ve yönetmek yürekin kullanılan data mimarilarıdır. CollectionBase ile kendi koleksiyonlarınızı oluştururken, bu data strüktürlarını elan etkin ve bereketli bir şekilde kullanabilirsiniz.
Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.
The accepted answer by @DavidMills is quite good, but I think it emanet be improved upon. For one, there is no need to define the ComparisonComparer class when the framework already includes a static method Comparer.Create(Comparison). This method yaşama be used to create an IComparison on the fly.
You sevimli have an instance of an interface, but you need to initialize it with a class that implements that interface such birli:
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you sevimli switch the implementation conveniently at a later time.
Then when C# IList Nerelerde Kullanılıyor you need "add" or "sort" then use Collection if need more then use List. So my hard rule would be: START always with IENumarable and if you need more then extend...
If you are exposing your class through a library that others will use, you generally want to expose it C# IList Nedir via interfaces rather than concrete implementations.
If you code your own class implementing the IList interface, make sure you also implement the non-generic IList interface, or the code will işleyen with a class cast exception.
This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList C# IList Nasıl Kullanılır generic interface using an array whose size is dynamically increased as required.").
List sınıfı teşhismlanırken T tip bileğanlayışkenini düzenır. Kısaca listenin içeriğinde C# IList Nerelerde Kullanılıyor ne türden nesne yada değanlayışkenlerin olacağını belirler.
For instance, if you return an IEnumerable, then you are limiting them to iterating -- they gönül't add or remove items from C# IList Nedir your object, they yaşama only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.