We needed the list indexer infrequently, so the inefficiency was not a mesele. 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.
Bir dahaki sefere versiyon yapmış olduğumda kullanılmak üzere hamleı, elektronik posta adresimi ve web site adresimi bu tarayıcıevet kaydet.
Also, it casts IList to IList which başmaklık the potential to be dangerous. In most cases that I have seen, List which implements IList is used behind the scenes to implement IList, but this is not guaranteed and can lead to brittle code.
Can a unique position be deduced if pieces are replaced by checkers (birey 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.
so its safety for you and freedom to the coder who is writing concrete implementation to change or add more functionality to his concrete class.
StuartLCStuartLC 106k1818 gold badges216216 silver badges289289 bronze badges Add a C# IList Nasıl Kullanılır comment
In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely together. It emanet be done, but it is a pain. Unfortunately since IList-of-T doesn't derive from IList there are cases where this hayat fail - but it is a good 95% rule.
The idea is C# IList Nasıl Kullanılır that you hide the implementation details from the user, and instead provide them with a stable interface. This is to reduce dependency on details that might change in the future.
Taking LinkedList vs taking C# IList Nedir List vs IList all communicate something of C# IList Nerelerde Kullanılıyor the performance guarantees required by the code being called.
It is like this other question. The other question shares a lot of common ground, but is arguably hamiş a true duplicate. In either case though, this is not opinion-based. What may have C# IList Neden Kullanmalıyız happened is that the closer might have just looked at this question's title, without reading the question itself. The body is objective.
Less ridiculous way to prove that an Ascii character compares equal with itself in Coq more hot questions
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it başmaklık everything you need.
additional advantage is that your code is safe from any changes to concrete class bey you are subscribing to only few of the methods of concrete class and those are the ones that are going to be there bey long kakım the concrete class inherits from the interface you are using.