You cannot predict the future. Assuming that a property's type will always be beneficial as a List is immediately limiting your ability to adapt to unforeseen expectations of your code.
Same principle kakım before, reversed. Offer the bare minimum that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
I think that, ideally, the .Kupkuru Framework would include a static sorting method that accepts an IList, but the next best thing is to create your own extension method. It's derece too hard to create a couple of methods that will allow you to sort an IList birli you would a List.
If you think that interfaces are useful only for building over-sized, grandiose architectures and have no place in small shops, then I hope that the person sitting across from you in the interview isn't me.
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.
Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .NET framework are so remote that it's theoretical jelly tots reserved for "best practices".
Inside the method, you should use var, instead of IList or List. When your veri source changes to come from a method instead, your onlySomeInts C# IList Neden Kullanmalıyız method C# IList Neden Kullanmalıyız will survive.
class Kisi string ad; string soyad; public string Ad get return ad; grup ad = value; public string Soyad get return soyad; takım soyad = value;
In most cases, if you are using a List and you think you could use a narrower interface C# IList Nedir instead - why not IEnumerable? This is often a better fit if you don't need to add items. If you need to add to the collection, use the concrete type, List.
Then later if you decide to convert the actual data store from a List to a Dictionary and expose the dictionary keys as the actual value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your class will no longer have that capability. That's a big problem! If you expose the List birli an IEnumerable you sevimli comfortably predict that your collection is not being modified externally. That C# IList Nerelerde Kullanılıyor is one of the powers of exposing List birli any of the above interfaces.
IList.IsFixedSize değerinin çakılı bir boyuta mevla olup olmadığını IList tamlayan bir kıymetiharbiye allıkır.
Less ridiculous way to prove that an Ascii character compares equal with itself in Coq more hot questions
In collections of contiguous elements, such kakım lists, the elements that follow the insertion point move down to accommodate the C# IList Kullanımı new element.
would I run into problems with this? Since could they not pass in an array(that saf a fixed size)? Would it be better maybe for a concrete List?