Temel İlkeleri C# IList Nasıl Kullanılır

Temel İlkeleri C# IList Nasıl Kullanılır

Blog Article

I know there özgü been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.

Then the person calling the method is free to call it with any data type that is enumerable. This allows your code to be used in unexpected, but perfectly valid ways.

Here's an example: I had a project once where our lists got very large, and resulting fragmentation of the large object heap was hurting performance. We replaced List with LinkedList. LinkedList does not contain an array, so all of a sudden, we had almost no use of the large object heap.

It's more nuanced than that. If you are returning an IList as part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.

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

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

GitHub'da bizimle ortaklaşa iş konstrüksiyonn Bu yürekğin kaynağı GitHub'da bulunabilir; burada antrparantez problemlerı ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Elan aşkın marifet ciğerin ulamada kâin kılavuzumuzu inceleyin.

Don't you know in advance if your method needs a list that emanet C# IList Nasıl Kullanılır take additional members; don't you specify that in the method signature? What exactly were you going to do if you were passed a read only list C# IList Neden Kullanmalıyız like int[]?

For collections you should aim to use IEnumerable where possible. This gives the most flexibility but C# IList Nedir is derece always suited.

tranmqtranmq 15.5k33 gold badges3232 silver badges2727 bronze badges 6 But in this case I C# IList Neden Kullanmalıyız hayat't bind my collection to DataGridView rather I have to expose the _list member in MyCollection.

On the other hand, when returning an object out of a function, you want to give the user the richest possible grup of operations without them having to cast around. So in that case, if it's a List internally, return a copy bey a List.

You might want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders kakım long bey they conform to "rules" defined by your IList or ICollection.

If you're just enumerating over the values, you should be using IEnumerable. Every type of datatype that can hold more than one value implements IEnumerable (or should) and makes your method hugely flexible.

There is a complication though that dynamic güç't see explicit implementations, so something yaşama implement IList and IList-of-T C# IList Kullanımı and yet still be completely unusable from dynamic.