Arraylist: Canlı boyutludur, eleman ekleme/silme teamüllemleri henüz kolaydır ve farklı bilgi türlerini saklayabilir.
Then the person calling the method is free to call it with any data type that is enumerable. This allows your code to be used in unexpected, but perfectly valid ways.
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 bey a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change it."
A List object allows you to create a list, add things to it, remove it, update it, index into it and etc. List is used whenever you just want a generic list where you specify object type in it and that's it.
ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't you just have to change that to the new type birli well? So maybe IList to IList?
Yes, you may never change that veri type from a List but you yaşama be sure that if you have to. Your code is ready for it.
However using a concrete implementation and List on a class that changes, could cause the calling code to need to be changed bey well. This is because a class adhering to IList guarantees a certain behavior that is derece guaranteed by a concrete type using List. Also having the power to do something like modify the default implementation of List on a class Implementing IList for say the .Add, .Remove or any other IList method gives the developer a lot
If you started with a concrete type and you decided to change to another one, even if it uses the same interface, you're going to break someone else's code unless C# IList Nerelerde Kullanılıyor you started off with an interface or abstract base type. Share Improve this answer Follow
If you sevimli consider your method, determine that you probably won't be changing the return collection type, then it is probably safe to return C# IList Kullanımı a more exact type. If you aren't sure, or are afraid that if you change it in future you'll be breaking other people's code, then go more general.
IList.IsFixedSize değerinin mıhlı bir boyuta iye olup olmadığını IList belirten bir ölçü kırmızıır.
Then I looked in my view(mvc) and found that I actually needed the count method bey I C# IList Nedir 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 hamiş need.
You yaşama pass a plain array to something C# IList Nedir which accepts an IList parameter, C# IList Nerelerde Kullanılıyor and then you güç call IList.Add() and will receive a runtime exception:
This works, because only the outer list is created in the first place. You kişi then insert individual items that are compatible with IList: