I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method as well kakım casting to a List but none of these seemed overly elegant.
Lütfen süflidaki kutuya şikayetinizin bilgilerinı edebiyat. Şikayetinizi değerlendirildikten sonra size olgun 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?
Sevimli a unique position be deduced if pieces are replaced by checkers (güç see piece color but hamiş type)
IList is a interface and doesn't have any implementation, so the performance of IList depending the class it implements
Convert your IList into List or some other generic collection and then you güç easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In most cases, if you are using a List and you think you could use a narrower interface instead - why hamiş 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.
If you hayat consider your method, determine that you probably won't be changing the return collection type, C# IList Neden Kullanmalıyız then it is probably safe to return a more exact type. If you aren't sure, or are afraid that if you change C# IList Kullanımı it in future you'll be breaking other people's code, then go more general.
Obviously if you are being asked which you use in C# IList Nasıl Kullanılır an interview, you say IList, smile, and both look pleased at yourselves for being so clever. Or for a public facing API, IList. Hopefully you get my point.
You might want to have an IOrderRepository that defines C# IList Kullanımı a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders bey long birli they conform to "rules" defined by your IList or ICollection.
If you're just enumerating over the values, you should be using IEnumerable. Every type of datatype that can hold more than one value implements IEnumerable (or should) and makes your method hugely flexible.
I read a lot of posts saying how this makes it easier to change the implementation later on, but I just don't fully see how that C# IList Nedir works.