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 kakım 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.
Bir dahaki sefere değerlendirme yapmış olduğumda kullanılmak üzere aşamaı, elektronik posta adresimi ve web şehir adresimi bu tarayıcıya kaydet.
Remove Silinmesini matlup kıymeti siler. Silinecek fehamet liste süresince yekten bir tomar olması durumunda ilk değeri kaldırır. Bu metodu çoklukla referans tipler ile değer çıkarmak muhtevain kullanılır. Fakat kırat tipleri ile bile kullanılabilir.
In this specific case since you're essentially talking about a language construct, not a custom one it generally won't matter, but say for example that you found List didn't support something you needed.
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 emanet't justify it, use the interface.
+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 sorun... Can I borrow the phrase "Architecture Astronauts"? I dirilik see it will come in handy.
3 @phoog: Considering where Eric is coming C# IList Nasıl Kullanılır from, it wouldn't be surprising he is more cautious about breaking changes. But it is definitely a valid point.
The idea is 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.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
It is like this other question. The other question shares a lot of C# IList Nedir common ground, but is arguably hamiş a true duplicate. In either case though, this is not 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 C# IList Nerelerde Kullanılıyor objective.
Bilgi Ambarlama: Uygulamalarda yolcu verileri yahut işleme esnasında oluşan verileri depolamak sinein kullanılabilir.
If you use the concrete type all callers need to be updated. C# IList Nasıl Kullanılır If exposed bey IList the caller doesn't have to be changed.
The other general reason for using C# IList Nedir interfaces is to expose the minimal amount of knowledge necessary to the user of an object. Consider the (contrived) case where I have a veri object that implements IList.