Note that, if your API is only going to be used in foreach loops, etc, then you might want to consider just exposing IEnumerable instead.
Maybe take it into a List of T rather than ArrayList, so that you get type safety and more options for how you implement the comparer.
Bu site, istenmeyenleri azaltmak derunin Akismet kullanıyor. Değerlendirme verilerinizin nasıl maslahatlendiği hakkında henüz bir küme malumat edinin.
Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.
The preceeding line of code will work, but you will only have the members of IList available to you instead of the full set from whatever class you initialize.
List is a specific implementation of IList, which is a container that sevimli be addressed the same way birli a linear array T[] using an integer index. When you specify IList birli the type of the method's argument, you only specify that you need certain capabilities of the container. For example, the interface specification does derece enforce C# IList Kullanımı a specific data structure to be used.
GitHub'da bizimle işbirliği yapın Bu gönülğin kaynağı GitHub'da bulunabilir; burada üste sorunları ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Daha okkalı bilim sinein yardımda bulunan kılavuzumuzu inceleyin.
If you specify C# IList Nasıl Kullanılır your methods to return an interface that means you are free to change the exact implementation later on without the consuming method ever knowing.
Bir dahaki sefere değerlendirme yaptığımda kullanılmak üzere girişimı, elektronik posta adresimi ve web şehir adresimi bu tarayıcıevet kaydet.
Modülerlik: Yazılım projelerinde modüler bir yaklaşım sunarak kod tekrarını azaltır ve hizmetı kolaylaştırır.
By asking for more than you need, you (1) make the caller do unnecessary work to satisfy your unnecessary demands, and (2) communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller has a sequence, they don't need to call ToList on it to satisfy your demand.
You might want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders kakım long birli they conform to "rules" defined by your IList or ICollection.
for your return types. This gives your callers the most flexibility in passing in types to your C# IList Nerelerde Kullanılıyor methods and the most opportunities to cast/reuse the return values.
Encapsulation relies on telling clients as little about the implementation of your class kakım possible. If you return a concrete List, you sevimli't C# IList Nedir then change to some other better type without forcing all C# IList Nerelerde Kullanılıyor of your clients to re-compile/update.