Hakkında herşey C# IList Nasıl Kullanılır

Hakkında herşey C# IList Nasıl Kullanılır

Blog Article

Note that, if your API is only going to be used in foreach loops, etc, then you might want to consider just exposing IEnumerable instead.

Arec BarrwinArec Barrwin 61.8k99 gold badges3030 silver badges2525 bronze badges 14 71 I have to disagree with your sardonic answer. I don't totally disagree with the sentiment of over-architecture being a real sıkıntı. However I think that especially in the case of collections that interfaces really shine.

Say I have a function that returns IEnumerable, inside the function I may use a List for an internal backing store to generate my collection, but I only want callers to enumerate it's contents, hamiş add or remove. Accepting an interface bey a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change it."

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 C# IList Neden Kullanmalıyız class when the framework already includes a static method Comparer.Create(Comparison). This method gönül be used to create an IComparison on the fly.

Convert your IList into List or some other generic collection and then you birey easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)

Most app-level code (i.e. the C# IList Kullanımı everyday code that ou write for your application) should probably focus on the generic versions; however there is also a lot of infrastructure code around that must use reflection.

In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics C# IList Nerelerde Kullanılıyor and reflection don't play nicely together. It emanet be done, but it is a pain. Unfortunately since IList-of-T doesn't derive from IList there are cases where this yaşama eden - but it is a C# IList Nasıl Kullanılır good 95% rule.

Anahtar bileğerleri tamlanan bir içinlaştırıcı kullanılarak C# IList Nedir zıtlaştırılır ve her grubun öğeleri belirtilen bir aksiyonlev kullanılarak yansıtılır.

class Kisi string ad; string soyad; public string Ad get return ad; takım ad = value; public string Soyad get return soyad; takım soyad = value;

 

List communicates "I need to get and kaş the elements of this sequence in arbitrary order and I only accept lists; I do hamiş accept arrays."

If you use a concrete implementation of list, another implementation of the same list will not be supported by your code.

Encapsulation relies on telling clients bey little about the implementation of your class kakım possible. If you return a concrete List, you can't then change to some other better type without forcing all of your clients to re-compile/update.