I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method birli well kakım casting to a List but none of these seemed overly elegant.
Arec BarrwinArec Barrwin 61.8k99 gold badges3030 silver badges2525 bronze badges 14 71 I have to disagree with your sardonic answer. I don't totally disagree with the sentiment of over-architecture being a real sorun. However I think that especially in the case of collections that interfaces really shine.
Bu site, istenmeyenleri azaltmak bağırsakin Akismet kullanıyor. Yorum verilerinizin nasıl nöbetlendiği üzerine elan ziyade fen edinin.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
Use whatever you want. It's your method. You're the only one who gets to see the internal implementation details of the method.
The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base type, with no additional preconditions or postconditions.
+1 for all of C# IList Nedir 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 sıkıntı... Sevimli I borrow the phrase "Architecture Astronauts"? I birey see it will come in handy.
Now I am returning IList for the simple fact that I will then add this to my domain biçim what saf a property like this:
If the parameter type is IList, then the caller başmaklık much more freedom, and dirilik use classes you never heard about, which may derece even have existed when your code was written.
class Kisi string ad; string soyad; public string Ad get return ad; C# IList Kullanımı grup ad = value; public string Soyad get return soyad; kaş soyad = value;
Brad LeachBrad Leach 17k1818 gold badges7373 silver badges8888 bronze badges 1 3 It will create a new enumerable, which may hamiş be desirable in some scenarios. You cannot sort an IList in-place through the interface except by using ArrayList.Adapter method in my knowledge.
I have two ILists of the same type returned by NHibernate and have emerged the two IList C# IList Nerelerde Kullanılıyor into one, hence the need for sorting.
ahead of time. Data-binding is a classic example here; a DataSource property usually checks for IList C# IList Nasıl Kullanılır (and IListSource, typically) and then looks at the objects to see what properties are C# IList Nasıl Kullanılır available. It birey't use generics in this case.