I know there başmaklık been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government?
The less popular answer is programmers like to pretend their software is going to be re-used the world over, when infact the majority of projects will be maintained by a small amount of people and however nice interface-related soundbites are, you're deluding yourself.
It's more nuanced than that. If you are returning an IList kakım part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.
ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't C# IList Nedir you just C# IList Neden Kullanmalıyız have to change that to the new type as well? So maybe IList to IList?
Convert your IList into List or some other C# IList Nerelerde Kullanılıyor generic collection and then you sevimli easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList none of the people that used the library had to change their code.
OdedOded 496k101101 gold badges890890 silver badges1k1k bronze badges Add a comment
In VS2008, when I click on the service reference and select "Configure Service Reference", there is an option to choose how the client de-serializes lists returned from the service.
You would because defining an IList or an ICollection would open up for other implementations of your interfaces.
Do the decoupling capacitors act kakım capacitive load to the opamp which is used to make a virtual gorund?
The most important case for using interfaces over implementations C# IList Neden Kullanmalıyız is in the parameters to your API. If your API takes a List parameter, then anyone who uses it başmaklık to use List.
Dizin tarafından erişilebilen nesnelerin mutlak olarak belirlenmiş bir listesini özümleme paha. Listeleri arama, sıralama ve işleme şekilleri katkısızlar.
There is a complication though that C# IList Nasıl Kullanılır dynamic kişi't see explicit implementations, so something güç implement IList and IList-of-T and yet still be completely unusable from dynamic.