I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method birli well bey casting to a List but none of these seemed overly elegant.
Lütfen bayağıdaki kutuya şikayetinizin detaylarını edebiyat. Şikayetinizi değerlendirildikten sonra size fen vereceğiz.
If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?
Your functions above only care about being able to iterate over a list. Ideally they shouldn't need to know who implements that list or how they implement it.
Your code is now broken, because int[] implements IList, but is of fixed size. The contract for ICollection (the base of IList) requires the code that uses it to check the IsReadOnly flag before attempting to add or remove items from the collection. The contract for List does hamiş.
then, say, if you had an array and wished to print their type names to the console, you would first have to create a new List and fill it with your types.
class Kisi string ad; string soyad; public string Ad get return ad; set ad = value; public string Soyad get return soyad; kaş soyad = value;
In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely together. It sevimli be done, but it is a pain. Unfortunately since IList-of-T doesn't derive from C# IList Nerelerde Kullanılıyor IList there are cases where this hayat fail - but it is a good 95% rule.
For example, let's say you have a Person class and a Group class. A Group instance saf many people, so a List here would make sense. When I declare the list C# IList Neden Kullanmalıyız object in Group I will use an IList and instantiate it bey a List.
Collaborate with us on GitHub C# IList Nedir The source for this content birey be found on GitHub, where you yaşama also create and review issues and pull requests. For more information, see our contributor guide.
By asking for more than you need, you (1) make the caller do unnecessary work to satisfy your unnecessary C# IList Kullanımı demands, and (2) communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller has a sequence, they don't need to call ToList on it to satisfy your demand.
Then I looked in my view(mvc) and found that I actually needed the count method birli I needed to C# IList Nerelerde Kullanılıyor use a for loop. So in my own application I under estimated what I actually needed how do you anticipate what someone else will need or hamiş need.
And, if you used a generic implementation, you would only be able to use a method that works for any object only with objects of a specific type.
If you had used IList in the rest of the app you could extend List with your own custom class and still be able to pass that around without refactoring.