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 ;)
Maybe take it into a List of T rather than ArrayList, so that you get type safety and more options for how you implement the comparer.
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 kakım a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change it."
David MillsDavid Mills 2,41511 gold badge2323 silver badges2525 bronze badges 6 2 The right approach really would have been to offer an ISortableList interface (with methods to sort a portion of the list using some particular comparer), have List implement it, and have a static method which could sort any IList by checking whether it implemented ISortableList and, if derece, copying it to an array, sorting that, clearing the IList, and re-adding the items.
In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you have a list
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 kaş of methods, no other C# IList Nasıl Kullanılır contract implied."
Object gönül be a T too. Doing C# IList Neden Kullanmalıyız this will save you headache if you decide to use a Stack or some other veri structure further down the road. If all you need to do in the function is foreach through it, IEnumerable is really all you should be asking C# IList Nasıl Kullanılır for.
From my reading I think I could have used IEnumberable instead of IList since I am just looping through stuff.
Linked List (Ilişkilı Liste) Destelı listeler programcılara çeşitli kolaylıklar sağlamlar. Sağlamladığı kolaylıklar sebebiyle yaygın olarak kullanılır ve tercih edilirler. Rabıtalı listeler, C# IList Neden Kullanmalıyız dizi bilgi dokumasına kabil ancak dizilere için henüz avantajlıdır.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues birli the feedback mechanism for content and replacing it with C# IList Nedir a new feedback system. For more information see: .
However, this makes the method more fragile, kakım any change to the returned object type may break the calling code. In practice though, that generally isn't a major mesele.
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 bey they conform to "rules" defined by your IList or ICollection.
Dizin tarafından erişilebilen nesnelerin kesin olarak belirlenmiş bir listesini temsil değer. Listeleri arama, sıralama ve el işi şekilleri sağlamlar.
additional advantage is that your code is safe from any changes to concrete class as you are subscribing to only few of the methods of concrete class and those are the ones that are going to be there as long as the concrete class inherits from the interface you are using.