Note that the IsReadOnly flag comes from ICollection, and indicates whether items sevimli be added or removed from the collection; but just to really confuse things, it does hamiş indicate whether they dirilik be replaced, which in the case of Arrays (which return IsReadOnlys == true) güç 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, derece 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.
IList is a interface and doesn't have any implementation, so the performance of IList depending the class it implements
The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base type, with no additional preconditions or postconditions.
Remove Silinmesini mergup değeri siler. Silinecek kıymet liste içre takkadak bir küme olması yerinde ilk kıymeti kaldırır. Bu metodu ekseri referans tipler ile C# IList Nasıl Kullanılır kıymetiharbiye çıkarmak derunin kullanılır. Ancak kıymet tipleri ile bile kullanılabilir.
OdedOded 496k101101 gold badges890890 silver badges1k1k bronze badges Add a comment
For example, let's say you have a Person class C# IList Nasıl Kullanılır and a Group class. A Group instance özgü many people, so a List here would make sense. When I declare the list object in Group I will use C# IList Nedir an IList and instantiate it as a List.
If you code your own class implementing the IList interface, make sure you also implement the non-generic IList interface, or the C# IList Kullanımı code will eden with a class cast exception.
Of course that only need apply to methods that are externally visible (i.e. public methods). I personally use interfaces even C# IList Nerelerde Kullanılıyor in internal code, but bey you are able to change all the code yourself if you make breaking changes it's derece strictly necessary.
Then I looked in my view(mvc) and found that I actually needed the count method birli I needed to use a for loop. So in my own application I under estimated what I actually needed how do you anticipate what someone else will need or not need.
So typically, your methods should accept and return interfaces for collections. This leaves your own implementation and your callers room to decide on the actual implementation as required.
Encapsulation relies on telling clients as little about the implementation of your class kakım possible. If you return a concrete List, you sevimli't then change to some other better type without forcing all of your clients to re-compile/update.