I know there başmaklık been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.
Lütfen bayağıdaki kutuya şikayetinizin detaylarını gökçe yazın. Şikayetinizi bileğerlendirildikten sonra size malumat vereceğiz.
Diyelim ki formunuzdaki textboxları listenize doldurdunuz yalnızca Text’i boş olan textboxları bulmanız gerekiyor. Bunun derunin List u kullanmanız gerekir. Yukarıda anlattığımız örneği mahdut olarak yapacak olursak;
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.
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 derece.
List is a specific implementation of IList, which is a container that yaşama be addressed the same way kakım 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 hamiş enforce a specific veri structure to be used.
Inside the method, you should use var, instead of IList or List. When your veri source changes to come from a method instead, your onlySomeInts method will C# IList Nerelerde Kullanılıyor survive.
Now I am returning IList for the simple fact that I will then add this to my domain benzer what katışıksız a property like this:
The idea is that you hide the implementation details from the user, and instead provide them with a stable interface. This is to reduce dependency on details that might change in the future.
The Cast function is just a reimplementation of the extension method that comes C# IList Neden Kullanmalıyız with 3.5 written kakım a düzgülü static method. It is quite ugly and verbose unfortunately.
By asking for more than you need, you (1) make the caller do unnecessary work to satisfy your unnecessary demands, C# IList Neden Kullanmalıyız and (2) communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller özgü a sequence, they don't need C# IList Nedir to call ToList on it to satisfy C# IList Kullanımı your demand.
Bilgi Ambarlama: Uygulamalarda eğreti verileri veya el işi esnasında oluşan verileri depolamak kucakin kullanılabilir.
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it başmaklık everything you need.
Have children's car seats derece been proven to be more effective than seat belts alone for kids older than 24 months?