Note that, if your API is only going to be used in foreach loops, etc, then you might want to consider just exposing IEnumerable instead.
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
Here's an example: I had a project once where our lists got very large, and resulting fragmentation of the large object heap was hurting performance. We replaced List with LinkedList. LinkedList does derece contain an array, so all of a sudden, we had almost no use of the large object heap.
Bearing this in mind, it makes most sense to pass types with the least number of external dependencies possible and to return the same. However, this could be different depending on the visibility of your methods and their signatures.
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.
IList on the other hand is an Interface. Basically, if you want to create your own custom List, say a list class called BookList, then you hayat use the Interface to give you basic methods and structure to your new class. IList is for when you want to create your own, special sub-class that implements List.
In case of using IList, the caller is always guareented things to work, and the implementer is free to change the underlying collection to any alternative concrete implementation of IList
However using a concrete implementation and List on a class that changes, could cause the calling code to need to be changed kakım well. This is because a class adhering to IList guarantees a certain behavior that is hamiş guaranteed by a concrete type using List. Also having the power C# IList Neden Kullanmalıyız 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
One Piece Şeytan Meyveleri Kitabı ile anime yazılarımıza devam edelim. Önceleri toparladığım bir makaslamakydı bu yazı. Bir anime izlerken o animeyi ne kadar çok sevdiğime…
Modülerlik: C# IList Kullanımı Mukayyetm projelerinde modüler bir yaklaşım sunarak C# IList Nerelerde Kullanılıyor şifre geneını azaltır ve bakımı kolaylaştırır.
IList.IsFixedSize değerinin durağan bir boyuta malik olup olmadığını IList tamlayan bir şayan allıkır.
List communicates "I need to get and kaş the elements of this sequence in arbitrary order and I only accept lists; C# IList Nedir I do derece accept arrays."
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 bey required.
So I have been playing C# IList Nerelerde Kullanılıyor around with some of my methods on how to do this. I am still not sure about the return type(if I should make it more concrete or an interface).