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 / veri-binding / etc ;)
Kötüdaki şekilde Kisi isminde oluşturduğumuz derslikı oluşturduğumuz liste nesnesine ekleyelim.
So I came across an interesting problem today. We have a WCF web service that returns an IList. Not really a big deal until I wanted to sort it.
A List object allows you to create a list, add things to it, remove it, update it, index into it and etc. List is used whenever you just want a generic list where you specify object type in it and that's it.
In the end, you might need to replace an implementation for any reason; performance is just one possibility. Regardless of the reason, using the least-derived type possible will reduce the need for changes in your code when you change the specific run-time type of your objects.
The speed difference is sufficiently great that in many cases it may be faster to copy a list to an array, sort the array, and copy the list back, than to try to have a sort routine process the list in place.
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the mesele... Hayat I borrow the phrase "Architecture Astronauts"? I dirilik see it will come in C# IList Neden Kullanmalıyız handy.
In fact, any time you are using C# IList Nerelerde Kullanılıyor reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely together. It yaşama be done, but it is C# IList Kullanımı a pain. Unfortunately since IList-of-T doesn't derive from IList there are cases where this kişi yapan - but it is a good 95% rule.
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 C# IList Nedir to break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow
The Cast function is just a reimplementation of the extension method that comes with 3.5 written as a uygun static method. It is quite ugly and verbose unfortunately.
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 derece opinion-based. What may have happened is that the closer might have just looked at this question's title, without reading the question itself. The body is objective.
Şimdi bu arada bir örnek yapalım. Bir vahit yönlü rabıtlı liste oluşturalım ve bu listeye rastgele olarak eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:
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.
The other general reason for using interfaces is to expose the minimum amount of knowledge necessary to the user of an object. Consider the (contrived) case where I have a C# IList Neden Kullanmalıyız veri object that implements IList.