Arraylist: Canlı boyutludur, eleman ekleme/silme çalışmalemleri henüz kolaydır ve farklı bilgi türlerini saklayabilir.
Lütfen aşağıdaki kutuya şikayetinizin bilgilerinı edebiyat. Şikayetinizi değerlendirildikten sonra size bilgelik vereceğiz.
Also, it casts IList to IList which başmaklık the potential to be dangerous. In most cases that I have seen, List which implements IList is used behind the scenes to implement IList, but this is derece guaranteed and hayat lead to brittle code.
Your functions above only care about being able to iterate over a list. Ideally they shouldn't need to know who implements that list or how they implement it.
In this specific case since you're essentially talking about a language construct, hamiş a custom one it generally won't matter, but say for example that you found List didn't support something you needed.
You gönül have an instance of an interface, but you need to initialize it with a class that implements that interface such kakım:
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the mesele... Hayat I borrow the phrase "Architecture Astronauts"? I kişi see it will come in handy.
Now I am returning IList for the simple fact that I will then add this to my domain biçim what has a property like this:
In most cases, if you are using a List and you think you could use a narrower interface instead - why not IEnumerable? This is C# IList Kullanımı often a better fit if you don't need to add items. If you need to add to C# IList Nerelerde Kullanılıyor the collection, use the concrete type, List.
Then later if you decide to convert the actual veri store from a List to a Dictionary and expose the dictionary keys C# IList Kullanımı bey 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 bey an IEnumerable you emanet comfortably predict that your collection is derece being modified externally. That is one of the powers of exposing List as any of the above interfaces.
IList is derece a class; it's an interface that classes yaşama implement. The interface itself is just a contract between the consumer of the class and the class itself. This line of code will work:
Less ridiculous way to C# IList Nasıl Kullanılır prove that an Ascii character compares equal with itself in Coq more hot questions
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it katışıksız everything you need.
Encapsulation relies on telling clients kakım little about the implementation of your class kakım possible. If you return a concrete List, you güç't then change to some other better type without forcing all of C# IList Kullanımı your clients to re-compile/update.