Else use List. You güç't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List not 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"
But far more importantly, if you are accepting an IList as a parameter you'd better be careful, because IList and List do not behave the same way. Despite the similarity in name, and despite sharing an interface
Diyelim ki formunuzdaki textboxları listenize doldurdunuz sadece Text’i boş olan textboxları bulmanız gerekiyor. Bunun dâhilin List u kullanmanız gerekir. Mafevkda anlattığımız örneği çarpık çurpuk olarak meydana getirecek olursak;
All concepts are basically stated in most of the answers above regarding why use interface over concrete implementations.
Kupkuru 4.6 (and it will likely be caught by the compiler). But there hayat be more insidious cases, such kakım passing a C# array as a IList. I am not sure everyone is aware arrays implement IList, which means support for Add should not be assumed.
Yes, you may never change that veri type from a List but you kişi be sure that if you have to. Your code is ready for it.
GitHub'da bizimle ortaklaşa iş mimarin Bu hapishaneğin kaynağı GitHub'da bulunabilir; burada ayrıca problemlerı ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Elan çokça bilim bağırsakin katkıda kâin kılavuzumuzu inceleyin.
Don't you know in advance if your method needs a list that hayat take additional members; don't you specify that in the method signature? C# IList Neden Kullanmalıyız What exactly were you going to do if you were passed a read only list like int[]?
Bir dahaki sefere versiyon yapmış olduğumda kullanılmak üzere adımı, elektronik posta adresimi ve web site adresimi bu tarayıcıevet kaydet.
It really comes down to the kind of functionality you need. I'd suggest using the List class C# IList Nedir in most cases. IList is best for when you need to make a custom array that could have some very specific rules that you'd like to encapsulate within a collection so you don't repeat C# IList Kullanımı yourself, but still want .NET to recognize it birli a list.
kemiller2002kemiller2002 115k2828 gold badges198198 silver badges253253 bronze badges Add a comment
I leave this up to show that if you needed to do it (e.g. the off chance a third party C# IList Nasıl Kullanılır library C# IList Nasıl Kullanılır returned a List that you needed to convert for another 3rd party library), you birey do it this way.
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.
This works, because only the outer list is created in the first place. You emanet then insert individual items that are compatible with IList: