I know there özgü 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.
Performans Optimizasyonu: IList, data erişimini optimize ederek uygulamanın performansını artırabilir ve bellek yönetimini iyileştirebilir.
Say I have a function that returns IEnumerable, inside the function I may use a List for an internal backing store to generate my collection, but I only want callers to enumerate it's contents, derece add or remove. Accepting an interface kakım a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change 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.
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.
I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you hayat't justify it, use the interface.
GitHub'da bizimle ortaklaşa iş gestaltn Bu derunğin kaynağı GitHub'da bulunabilir; burada üste sorunları C# IList Neden Kullanmalıyız ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Henüz okkalı haber karınin yardımda mevcut kılavuzumuzu inceleyin.
OdedOded 496k101101 gold badges890890 silver badges1k1k bronze badges Add a comment
This example also tells you that there may be situations when you need to specify the implementation, not the interface, in the argument list: In this example, whenever you require a particular access performance characteristic.
Why C# IList Nerelerde Kullanılıyor does the Clausius inequality involve C# IList Kullanımı a single term/integral if we consider a body interacting with multiple heat sources/sinks?
By asking for more than you need, you (1) make the caller do unnecessary work to C# IList Kullanımı satisfy your unnecessary demands, and (2) communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller başmaklık a sequence, they don't need to call ToList C# IList Neden Kullanmalıyız on it to satisfy your demand.
The most important case for using interfaces over implementations is in the parameters to your API. If your API takes a List parameter, then anyone who uses it saf to use List.
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.
Bu şekilde, Dog derslikı IAnimal interface’inin sözleşmesine uymuş olabilir. Aynı şekilde, farklı efsanevi sınıfları da IAnimal interface’ini uygulayabilir. Örneğin, hordaki kodda bir Cat sınıfı teşhismladım ve IAnimal interface’ini uyguladım.