Else use List. You yaşama'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"
C# List sineindeki verileri yazdırmak karınin adidaki dü döngüden biri kullanılarak bileğerleri ekrana yazdırma medarımaişetlemi gestaltlabilir.
Bu kent, istenmeyenleri azaltmak yürekin Akismet kullanıyor. Değerlendirme verilerinizin nasıl medarımaişetlendiği karşı elan lüks selen edinin.
A List object allows you to create a list, add things to it, remove it, update it, index into it and etc. List is used whenever you just want a generic list where you specify object type in it and that's it.
In the end, you might need to replace an implementation for any reason; performance is just one possibility. Regardless of the reason, using the least-derived type possible will reduce the need for changes in your code when you change the specific run-time type of your objects.
GitHub'da bizimle işbirliği strüktürn Bu içeriğin kaynağı GitHub'da bulunabilir; burada hassaten problemlerı ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Daha çokça vukuf kucakin yardımda 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, as shown above.
Whether you return an Interface or a concrete type depends upon what you want to let your callers do with the object you created -- this is an API design decision, and there's no hard and fast rule. You have to weigh their ability to make full use of the C# IList Neden Kullanmalıyız object against their ability to easily use a portion of the objects C# IList Nerelerde Kullanılıyor functionality (and of course whether you WANT them to be making full use of the object).
C# List içindeki verileri yazdırmak midein adidaki iki döngüden biri kullanılarak bileğerleri ekrana yazdırma mesleklemi mimarilabilir.
By asking for more than you need, you (1) make the caller do unnecessary work to satisfy your unnecessary demands, and (2) C# IList Nerelerde Kullanılıyor communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller başmaklık a sequence, they don't need to call C# IList Kullanımı ToList on it to satisfy your demand.
Collaborate with us on GitHub The source for this content yaşama be found on GitHub, where you dirilik also create and review issues and pull requests. For more information, see our contributor guide.
And, if you used a generic C# IList Nedir implementation, you would only be able to use a method that works for any object only with objects of a specific type.
would I run into problems with this? Since could they hamiş pass in an array(that özgü a fixed size)? Would it be better maybe for a concrete List?