We needed the list indexer infrequently, so the inefficiency was hamiş a problem. If it had been, we could have provided some other implementation of IList, perhaps kakım a collection of small-enough arrays, that would have been more efficiently indexable while also avoiding large objects.
1 @supercat: What could ISortableList offer that's derece 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?
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 not contain an array, so all of a sudden, we had almost no use of the large object heap.
Emanet a unique position be deduced if pieces are replaced by checkers (gönül see piece color but hamiş type)
Basically, I need to see some actual code examples of how using IList would have solved some sorun over just taking List into everything.
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 güç 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.
StuartLCStuartLC 106k1818 C# IList Nasıl Kullanılır gold badges216216 silver badges289289 bronze badges Add a comment
Ask those people what they'd like the methods to return. Your question is fundamentally "how do I know what software to write?" You know by getting to know what problems your customer özgü to solve, and writing code that solves their problems.
If you started with a concrete type and you decided to change to another one, even if it uses the same interface, you're going to break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow
It really comes down to the kind of functionality you need. I'd suggest using the List class in most cases. IList C# IList Kullanımı is best for when you need to make a custom array that could have some very specific rules that you'd like to encapsulate within a collection so you don't repeat yourself, but still want .Kemiksiz to recognize it birli a list.
Of course that only need apply to methods C# IList Nedir that are externally visible (i.e. public methods). I personally use interfaces even in internal code, but kakım you are able to change all the code yourself if you make C# IList Nerelerde Kullanılıyor breaking changes it's not strictly necessary.
In this case you could pass in any class which implements the IList interface. If you used List instead, only a List instance could be passed in.
And, if you used a generic implementation, C# IList Nasıl Kullanılır you would only be able to use a method that works for any object only with objects of a specific type.
ahead of time. Data-binding is a classic example here; a DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what properties are available. It emanet't use generics in this case.