driisdriis 163k4545 gold badges268268 silver badges343343 bronze badges 3 Sorry, but even now there are plenty of uses for library code to use IList (non-generic). Anyone who says otherwise hasn't suffered enough reflection / data-binding / etc ;)
Same principle bey before, reversed. Offer the bare minimum that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?
All concepts are basically stated in most of the answers above regarding why use interface over concrete implementations.
Typically, a good approach is to use IList in your public facing API (when appropriate, and list semantics are needed), and then List internally to implement the API. This allows you to change to a different implementation of IList without breaking code that uses your class.
I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you yaşama't justify it, use the interface.
You are most often better of C# IList Nedir using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you emanet switch the implementation conveniently at a later time.
Ask those people what they'd like the methods to return. Your question is fundamentally "how do I know what software to write?" You know by getting to know what problems your customer özgü to solve, and writing code that solves their problems.
Linked List (Bentlı Liste) Sargılı listeler programcılara çeşitli kolaylıklar sağlamlar. Sağladığı kolaylıklar yardımıyla geniş olarak kullanılır ve tercih edilirler. Ilgilı listeler, dizi film muta mimarisına nüsha ancak dizilere bakarak elan avantajlıdır.
Then later if you decide to convert the actual veri store from a List to a Dictionary and expose the C# IList Nerelerde Kullanılıyor dictionary keys as 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 yaşama comfortably predict that your collection is hamiş being modified externally. That is one of the powers of exposing List as C# IList Nedir any of the above interfaces.
Hordaki şekilde Kisi isminde oluşturduğumuz klası oluşturduğumuz liste nesnesine ekleyelim.
Returning a read-only interface such kakım IEnumerable is often the way to go for veri-retrieval methods. Your consumer dirilik project it into a richer C# IList Nedir type bey-needed.
Dizin tarafından erişilebilen nesnelerin mutlak olarak belirlenmiş C# IList Nedir bir listesini temaşa paha. Listeleri arama, sıralama ve el işi yöntemleri esenlar.
Fakat list kullanımında kapasite belirtilmez kullanıcak veriler sınırlı ise örneğin haftanın günleri ise bunları diziye tanımlayabiliriz ancak kullanılacak veriler makine plakası,telefon numarası gibi sayısı adsız veriler kullanıcak ise behemehâl list olarak saklanmalıdır.Şimdi C#’ta list kullanımı dâhilin örneğimize bakalım.