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 / data-binding / etc ;)
Same principle bey before, reversed. Offer the bare minimal that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
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.
Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:
I tend to follow Jeffrey's advice for internal code, but for a public library, I would probably be more inclined to follow Eric's.
You güç have an instance of an interface, but you need to initialize it with a class that implements that interface such kakım:
List implements IList, C# IList Kullanımı and so dirilik be assigned to the variable. There are also other types that also implement IList.
If you specify your methods to return an interface that means you are C# IList Neden Kullanmalıyız free to change the exact implementation C# IList Kullanımı later on without the consuming method ever knowing.
; being aware of the definition of the C# IList Nasıl Kullanılır interface ie. all abstract methods that are there to be implemented by any class inheriting the interface. so if some one makes a huge class of his own with several methods besides the ones he inherited from the interface for some addition functionality, and those are of no use to you, its better to use a reference to a subclass (in this case the interface) and assign the concrete class object to it.
Taking LinkedList vs taking List vs IList all communicate something of the performance guarantees required by the code being called.
Süflidaki şekilde Kisi isminde oluşturduğumuz sınıfı oluşturduğumuz liste nesnesine ekleyelim.
This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased bey C# IList Nerelerde Kullanılıyor required.").
When talking about return types, the more specific you are, the more flexible callers güç be with it.
Have children's car seats hamiş been proven to be more effective than seat belts alone for kids older than 24 months?