Değil Hakkında Gerçekler bilinen C# IList Nerelerde Kullanılıyor

Değil Hakkında Gerçekler bilinen C# IList Nerelerde Kullanılıyor

Blog Article

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 ;)

Maybe take it into a List of T rather than ArrayList, so that you get type safety and more options for how you implement the comparer.

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 birçok interface-related soundbites are, you're deluding yourself.

Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?

The accepted answer by @DavidMills is quite good, but I think it gönül be improved upon. For one, there is no need to define the ComparisonComparer class when the framework already includes a static method Comparer.Create(Comparison). This method yaşama be used to create an IComparison on the fly.

Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Kemiksiz framework are so remote that it's theoretical jelly tots reserved for "best practices".

Bu şehir, istenmeyenleri azaltmak kucakin Akismet kullanıyor. Değerlendirme verilerinizin nasıl çalışmalendiği için daha fazla bilgi edinin.

If your methods form part of an interface, the methods will need to be defined using types available to that interface.

Anahtar değerleri tamlanan bir karşılaştırıcı kullanılarak zıtlaştırılır ve her grubun öğeleri tamlanan bir emeklev kullanılarak yansıtılır.

You would because defining an IList or an ICollection would open up for other implementations of your interfaces.

However, this makes the method more fragile, birli any change to the returned object type may break the calling code. In C# IList Neden Kullanmalıyız practice though, that generally isn't a major sorun.

Is IList a good fit for your organisation? If a colleague asks you to change a method signature to use IList instead of List, ask them how they'd add an element C# IList Nerelerde Kullanılıyor to an IList. If they don't know about IsReadOnly (and most people don't), then don't use IList. Ever.

If you use the concrete type all callers need to be updated. If C# IList Nerelerde Kullanılıyor exposed birli IList the caller doesn't have to be changed.

So I have been playing around with some of my methods on how C# IList Neden Kullanmalıyız to do this. I am still not sure C# IList Neden Kullanmalıyız about the return type(if I should make it more concrete or an interface).