Else use List. You güç't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List hamiş an IList, else you are breaking Liskov substitution principle: "if S is a subtype of T, then objects of type T may be replaced with objects of type S"
Same principle kakım before, reversed. Offer the bare asgari that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
I think that, ideally, the .NET Framework would include a static sorting method that accepts an IList, but the next best thing is to create your own extension method. It's derece too hard to create a couple of methods that will allow you to sort an IList bey you would a List.
Kendi koleksiyon sınıflarınızı oluştururken yeni baştan kullanılabilir kod yazmanızı katkısızlar: C# CollectionBase kullanarak genel derlem çalışmalemlerini bâtınaziz bir bel kemiği klas oluşturabilirsiniz.
Basically, I need to see some actual code examples of how using IList would have solved some mesele over just taking List into everything.
In some code this can be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this takım of methods, no other contract implied."
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList none of the people that used the library had to change their code.
3 @phoog: Considering where Eric is coming from, it wouldn't be surprising he is more cautious about breaking changes. But it is definitely a valid point.
the method, it yaşama make a huge difference -- if they have an array and you're asking for a list, they have to change the array to a list or v.v. whenever calling the method, a total waste of time from both a programmer and performance POV.
Collaborate with us on GitHub The source for this content yaşama be found on GitHub, where you kişi also C# IList Neden Kullanmalıyız create and review issues and pull requests. For more information, see our contributor guide.
Do the decoupling capacitors act birli capacitive load to the opamp which is used to make a virtual gorund?
You might want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders bey long birli they conform to "rules" defined by your IList or ICollection.
for your return types. This gives your callers C# IList Nerelerde Kullanılıyor the most flexibility in passing in types to your methods and the most opportunities to cast/reuse the return values.
IEnumerable allows you to iterate through a collection. ICollection builds on this and C# IList Nedir also allows for adding and removing items. IList also allows for accessing and modifying them at a specific index. By exposing C# IList Nasıl Kullanılır the one that you expect your consumer to work with, you are free to change your implementation. List happens to implement C# IList Nerelerde Kullanılıyor all three of those interfaces. If you expose your property birli a List or even an IList when all you want your consumer to have is the ability to iterate through the collection. Then they could come to depend on the fact that they sevimli modify the list.