Note that the IsReadOnly flag comes from ICollection, and indicates whether items hayat be added or removed from the collection; but just to really confuse things, it does derece indicate whether they hayat be replaced, which in the case of Arrays (which return IsReadOnlys == true) hayat be.
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
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.
Sıfır ast hadına ehil birlik boyutlu diziler otomatik olarak uygular IList. Bu, diziler ve gayrı derlem türleri ortada yineleme edinmek karınin aynı kodu kullanabilen genel yöntemler oluşturmanıza olanak teşhisr.
swilliamsswilliams 48.6k2727 gold badges101101 silver badges130130 bronze badges 3 5 why derece make it a just a List in the first place? I still don't understand why bonus you get from making it a IList then in the constructor you make it into a List
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
You may hamiş ever need that option, but it's an argument. I think it's the entire argument for returning the interface instead of the concrete type. It's worth mentioning, but in this case it katışıksız a serious flaw.
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 with your argument, than you could argue to never use any interface at all, because some implementation of it might throw.
If C# IList Nasıl Kullanılır you are exposing your class through a library that others will use, you generally want to expose it via interfaces rather than concrete implementations.
You would because defining an IList or an ICollection would open up for other implementations of your interfaces.
If you're working within a single method (or even in a single class or assembly in some cases) and no one outside is going to see what you're doing, use the fullness of a C# IList Nerelerde Kullanılıyor List. But if you're interacting with outside code, like when you're returning a list from a method, then you only want to declare the interface without necessarily tying yourself to a specific implementation, especially if you C# IList Neden Kullanmalıyız have no control over who compiles against your code afterward.
The most important case for using interfaces over implementations is in the parameters to your API. If your API takes a List parameter, then anyone who uses C# IList Neden Kullanmalıyız it saf to use List.
If you use a concrete implementation C# IList Kullanımı of list, another implementation of the same list will derece be supported by your code.
additional advantage is that your code is safe from any changes to concrete class bey you are subscribing to only few of the methods of concrete class and those are the ones that are going to be there kakım long as the concrete class inherits from the interface you are using.