It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.
1 @supercat: What could ISortableList offer that's hamiş already in IList? Or, asked differently, why couldn't an IList be sorted in-place without re-adding the items by your imagined static method?
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, hamiş add or remove. Accepting an interface as 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 not, copying it to an array, sorting that, clearing the IList, and re-adding the items.
In this specific case since you're essentially talking about a language construct, derece a custom one it generally won't matter, C# IList Kullanımı but say for example that you found List didn't support something you needed.
Convert your IList into List or some other generic collection and then you sevimli easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)
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
Now I am returning IList for the simple fact that I will then add this to my domain manken what saf a property like this:
This example also tells you that there may be situations when you need to specify the implementation, derece the interface, in the argument list: In this example, whenever you require a particular access C# IList Nerelerde Kullanılıyor performance characteristic.
Collaborate with us on GitHub The source for this content yaşama be found on GitHub, where you dirilik also 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?
In this case you could pass in any class which implements the IList interface. If you used List instead, only a List C# IList Kullanımı instance could be passed in.
for your return types. This gives your callers the most flexibility in passing in types to your methods and the most opportunities to cast/reuse the return values.
ahead of time. Veri-binding is a classic example here; a DataSource property usually checks for IList (and IListSource, typically) and then looks C# IList Nedir at the C# IList Nedir objects to see what properties are available. It yaşama't use generics in this case.