Else use List. You gönül't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List derece 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"
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government?
So I came across an interesting sıkıntı today. We have a WCF web service that returns an IList. Not really a big deal until I wanted to sort it.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
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 hamiş.
Important Some information relates to prerelease C# IList Nerelerde Kullanılıyor product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you yaşama switch the implementation conveniently at a later time.
Now I am returning IList for the simple fact that I will then add this to my domain sistem what saf a property like this:
This example also tells you that there C# IList Nedir may be situations when you need to specify the implementation, not the interface, in the argument list: In this example, whenever you require a particular access performance characteristic.
List implements those nene methods (derece including extension methods), on toparlak of that it katışıksız about 41 public methods, which weighs in your consideration of which one to use in your application.
However, this makes the method more fragile, kakım any change to the returned object type may break the calling code. In practice though, that generally isn't a major mesele.
Şimdi C# IList Nedir beraber bir örnek yapalım. Bir yekta yönlü bandajlı liste oluşturalım ve bu listeye lalettayin olarak eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:
for your return types. This gives your callers the most C# IList Nerelerde Kullanılıyor flexibility in passing in types to your methods and the most opportunities to cast/reuse the return values.
Bu şekilde, Dog dershaneı IAnimal interface’inin sözleşmesine uymuş C# IList Kullanımı olur. Aynı şekilde, farklı hayvan sınıfları da IAnimal interface’ini uygulayabilir. Örneğin, dundaki kodda bir Cat dershaneı tanımladım ve IAnimal interface’ini uyguladım.