5 Basit Teknikleri için C# IList Kullanımı

5 Basit Teknikleri için C# IList Kullanımı

Blog Article

Note that the IsReadOnly flag comes from ICollection, and indicates whether items güç be added or removed from the collection; but just to really confuse things, it does not indicate whether they sevimli be replaced, which in the case of Arrays (which return IsReadOnlys == true) emanet be.

Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.

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, not add or remove. Accepting an interface kakım 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.

In this specific case since you're essentially talking about a language construct, derece a custom one it generally won't matter, but say for example that you found List didn't support something you needed.

I would turn the question around a bit, instead of C# IList Nedir 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 sevimli't justify it, use the interface.

StuartLCStuartLC 106k1818 gold badges216216 C# IList Neden Kullanmalıyız silver badges289289 bronze badges Add a comment  

IList is an Interface, hamiş a class. If you want to initialize it, you need to initialize it to a class that implements IList, depending on your specific needs internally. Usually, IList is initialized with a List.

For example, let's say you have a Person class and a Group class. A Group instance katışıksız many people, so a List here would make sense. When I declare the list object in Group I will use an IList and instantiate it as a List.

API Entegrasyonu: Dış API'lerden allıkınan verileri öğretmek ve yönetmek bağırsakin kullanılabilir, bu da icraat arası muta aksataini kolaylaştırır.

However, this makes the method more fragile, kakım any change to the C# IList Neden Kullanmalıyız returned object type may break the calling C# IList Nasıl Kullanılır code. In practice though, that generally isn't a major mesele.

This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased as required.").

You accept an Interface kakım a parameter for a method because that allows the caller to submit different concrete types birli arguments. Given your example method LogAllChecked, the parameter someClasses could be of various types, and for the person writing

This works, because only the outer list C# IList Kullanımı is created in the first place. You gönül then insert individual items that are compatible with IList: