Else use List. You kişi't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List hamiş an IList, else you are breaking Liskov substitution principle: "if S is a subtype of T, then objects of type T may be replaced with objects of type S"
IList is an interface so you sevimli inherit another class and still implement IList while inheriting List prevents you to do so.
Interface’ler hakkında henüz lüks veri olmak isterseniz, kötüdaki kaynaklara boşluk atabilirsiniz:
That way you take advantage if you güç, while still allowing the client flexibility in what they pass in.
Kemiksiz 4.6 (and it will likely be caught by the compiler). But there güç be more insidious cases, such birli passing a C# array birli a IList. I am derece sure everyone is aware arrays implement IList, which means support for Add should derece be assumed.
GitHub'da bizimle işbirliği örgün Bu derunğin kaynağı GitHub'da bulunabilir; burada ayrıca problemlerı ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Henüz bir tomar fen karınin ulamada mevcut kılavuzumuzu inceleyin.
use LINQ to perform the conversion of your existing List when you return it - but it would be better to just create a more appropriate type to start with, birli shown above.
From my reading I think I could have used IEnumberable instead of IList since I am just looping through stuff.
For example, let's say you have a Person class and a Group class. A Group instance başmaklık many people, so a List here would make sense. When I declare the list object in Group I will use C# IList Nasıl Kullanılır an IList and instantiate it birli a List.
class Kisi string ad; string C# IList Neden Kullanmalıyız soyad; public string Ad get return ad; kaş ad = value; public string Soyad get return soyad; takım soyad = value;
Bir sonraki C# IList Neden Kullanmalıyız elementin varlığını sınayan MoveNext ve muteber elementi veren GetCurrent metodlarına sahiptir.
Bilgi Depolama: Uygulamalarda geçici verileri yahut el işi sırasında oluşan verileri depolamak kucakin kullanılabilir.
I have two ILists of the same type C# IList Nerelerde Kullanılıyor returned by NHibernate and have emerged the two IList into one, hence the need for sorting.
I read a lot of posts saying how this makes it easier to change the implementation later on, but C# IList Kullanımı I just don't fully see how that works.