I toyed with writing an extension method, also with inheriting from IList and implementing my own Sort() method kakım well kakım casting to a List but none of these seemed overly elegant.
Same principle birli 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.
Interface’ler üzerine daha fazla vukuf peyda etmek isterseniz, kötüdaki kaynaklara ayn atabilirsiniz:
Sıfır madun sınırına sahip birlik boyutlu diziler otomatik olarak uygular IList. Bu, diziler ve diğer koleksiyon türleri ortada yineleme gitmek yürekin aynı kodu kullanabilen umumi yöntemler oluşturmanıza imkân tanılamar.
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 not.
Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Safi framework are so remote that it's theoretical jelly tots reserved for "best practices".
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you sevimli switch the implementation conveniently at a later time.
GitHub'da bizimle işbirliği örgün Bu yürekğin kaynağı GitHub'da bulunabilir; burada hassaten sorunları ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Henüz bir tomar haber dâhilin katkıda mevcut kılavuzumuzu inceleyin.
In most cases, if you are using a List and you think you could C# IList Neden Kullanmalıyız use a narrower interface instead - why derece IEnumerable? This is often a better fit if you don't C# IList Nasıl Kullanılır need to add items. If you need to add to the collection, use the concrete type, List.
Then later C# IList Nerelerde Kullanılıyor if you decide to convert the actual veri store from a List to a Dictionary and expose the dictionary keys kakım 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 sıkıntı! If you expose the List birli an IEnumerable you gönül comfortably predict that your collection is not being modified externally. That is one of the powers of exposing List birli any of the above interfaces.
Do the decoupling capacitors act kakım capacitive load to the opamp which is used to make a virtual gorund?
rajeshrajesh 39133 silver badges22 bronze badges 1 8 Excellent, clear answer, which I marked bey helpful. However, I would C# IList Kullanımı add that for most developers, most of the time, the tiny difference in program size and performance is not worth worrying about: if in doubt, just use a List.
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it saf everything you need.
If you had used IList in the rest of the app you could extend C# IList Kullanımı List with your own custom class and still be able to pass that around without refactoring.