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# CollectionBase derslikı, özelleştirilebilir koleksiyonların oluşturulmasını sağlamlar ve bu sayede mukayyetm projelerinde suples ve yeni baştan kullanılabilirlik esenlar.
Using IList instead of List makes writing unit tests significantly easier. It allows you to use a 'Mocking' library to pass and return veri.
It's more nuanced than that. If you are returning an IList birli part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.
In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you have a list
Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
The cost to do this is minimal, why derece save yourself the headache later? It's C# IList Nerelerde Kullanılıyor what the interface principle is all about.
Matthew WatsonMatthew Watson 108k1111 gold badges170170 silver badges290290 bronze badges 2 2 This is trivially true for every interface. If you want to follow through C# IList Nedir with your argument, than you could argue to never use any interface at all, because some implementation of it might throw.
For collections you should aim C# IList Kullanımı to use IEnumerable where possible. This gives the C# IList Neden Kullanmalıyız most flexibility but is hamiş always suited.
Then later if you decide to convert the actual data store from a List to a Dictionary C# IList Nerelerde Kullanılıyor and expose the dictionary keys birli the actual value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your class will no longer have that capability. That's a big sorun! If you expose the List kakım an IEnumerable you dirilik comfortably predict that your collection is derece being modified externally. That is one of the powers of exposing List bey any of the above interfaces.
kemiller2002kemiller2002 115k2828 gold badges198198 silver badges253253 bronze badges Add a comment
Less ridiculous way to prove that an Ascii character compares equal with itself in Coq more hot questions
List klası teşhismlanırken T tip bileğalışverişkenini allıkır. Yani listenin muhteviyatında hangi türden nesne yada değişkenlerin olacağını belirler.
The other general reason for using interfaces is to expose the asgari amount of knowledge necessary to the user of an object. Consider the (contrived) case where I have a data object that implements IList.