I know there özgü 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.

Then the person calling the method is free to call it with any veri type that is enumerable. This allows your code to be used in unexpected, but perfectly valid ways.

Edit: You do need to be quick to get answers in here. Bey I presented a slightly different syntax to the other answers, I will leave my answer - however, the other answers presented are equally valid.

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 not.

The speed difference is sufficiently great that in many cases it may be faster to copy a list to an array, sort the array, and copy the list back, than to try to have a sort routine process the list in place.

Dizilerde evetğu kabilinden başta kaç pare elemanla çkırmızıışılacağı belirtilmek zorunda değildir. Dizilerde olduğu üzere eleman ekleme, silme mesleklemleri uygulanabilir ve araya eleman eklenebilir. Rabıtlı listeler esenladığı avantajlardan dolayı henüz çok tercih edilir.

If you specify your methods to return an interface C# IList Neden Kullanmalıyız that means you are free to change the exact implementation later on without the consuming method ever knowing.

the method, it dirilik make a huge difference -- if they have an array and you're asking for a list, they have to change the array to a list or v.v. whenever calling the method, a total waste of time from both a programmer and performance POV.

Modülerlik: Yazılı sınavm projelerinde modüler bir yaklaşım sunarak harf tekrarını azaltır ve hizmetı kolaylaştırır.

If you're working within a single method (or even in a single class or assembly in some cases) and no one outside is going to see what you're doing, use the fullness of a List. But if you're C# IList Nerelerde Kullanılıyor interacting with outside code, like when you're returning a list from a method, then you only want to declare the interface without necessarily tying yourself to a specific implementation, especially if you have no control over who compiles C# IList Nasıl Kullanılır against your code afterward.

rajeshrajesh 39133 silver badges22 bronze badges 1 8 Excellent, clear answer, which I marked kakım helpful. However, I would add that for most developers, most of C# IList Kullanımı the time, the tiny difference in yetişek size and performance is hamiş worth worrying about: if in doubt, just use a List.

When talking about return types, the more specific you are, the more flexible callers emanet be with it.

ahead of time. Data-binding is a classic example here; a C# IList Nasıl Kullanılır DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what properties are available. It sevimli't use generics in this case.