Else use List. You sevimli't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List not 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"
From this it follows that your method implementation yaşama represent its local variables however you wish. The implementation details are not exposed. Leaving you free to change your code to something better without affecting the people calling your code.
I think that, ideally, the .Kemiksiz 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 kakım you would a List.
That way you take advantage if you emanet, while still allowing the client flexibility in what they pass in.
Hassaten mafevkda anlattığımız IndexOf metodunu Temel liste üzerinden zir listelerdeki elemanlar bağırsakin kullanamazsınız. Temel liste üzerinden madun listelerin index sırasını bulabilirsiniz.
This level of abstraction goes the other direction when it belongs to method parameters. When you pass your list to a method that accepts IEnumerable you birey be sure that your list is not going to be modified. When you are the person implementing the method and you say you accept an IEnumerable because all you need to do C# IList Neden Kullanmalıyız is iterate through that list.
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you birey switch the implementation conveniently at a later time.
If the collection is indexed, the indexes of the elements that are moved are also updated. This behavior does derece apply to collections where C# IList Neden Kullanmalıyız elements are conceptually grouped into buckets, such kakım a hash table.
For collections you should aim to use IEnumerable where possible. This gives the most flexibility but is C# IList Neden Kullanmalıyız hamiş always suited.
If you code your own class implementing the IList interface, make sure you also implement the C# IList Neden Kullanmalıyız non-generic IList interface, or the code will eden with a class cast exception.
Bir sonraki elementin varlığını sınayan MoveNext C# IList Nasıl Kullanılır ve muteber elementi veren GetCurrent metodlarına sahiptir.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: .
This will help if you decide to change the implementation of your class later to use a different concrete class. In that case the users of your library won't need to update their code since the interface doesn't change.
Encapsulation relies on telling clients birli little about the implementation of your class bey possible. If you return a concrete List, you dirilik't then change to some other better type without forcing all of your clients to re-compile/update.