Bir Unbiased Görünüm C# IList Nasıl Kullanılır

Bir Unbiased Görünüm C# IList Nasıl Kullanılır

Blog Article

The following example demonstrates the implementation of the IList interface to create a simple, fixed-size list. This code is part of a larger example for the IList interface.

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 problem. However I think that especially in the case of collections that interfaces really shine.

You pass the interface so that no matter what concrete implementation of that interface you use, your code will support it.

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

Kupkuru 4.6 (and it will likely be caught by the compiler). But there gönül be more insidious cases, such bey passing a C# array as a IList. I am hamiş sure everyone is aware arrays implement IList, which means support for Add should hamiş be assumed.

In some code this can be quite important and using concrete classes communicates C# IList Nerelerde Kullanılıyor your intent, your need for that specific class. An C# IList Nedir interface on the other hand says "I just need to call this grup of methods, no other contract implied."

I thought I'd never need to C# IList Nedir change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only C# IList Nedir returned an IList none of the people that used the library had to change their code.

Don't you know in advance if your method needs C# IList Nerelerde Kullanılıyor a list that güç 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 like int[]?

For collections you should aim to use IEnumerable where possible. This gives the most flexibility but is not always suited.

API Entegrasyonu: Dış API'lerden tuzakınan verileri geçmek ve yönetmek karınin kullanılabilir, bu da uygulamalar arası muta ahzüitaini kolaylaştırır.

kemiller2002kemiller2002 115k2828 gold badges198198 silver badges253253 bronze badges Add a comment  

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.").

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

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