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.

C# CollectionBase sınıfı, özelleştirilebilir koleksiyonların oluşturulmasını sağlamlar ve bu sayede nominalm projelerinde elastikiyet ve gene kullanılabilirlik sağlamlar.

Here's an example: I had a project once where our lists got very large, and resulting fragmentation of the large object heap was hurting performance. We replaced List with LinkedList. LinkedList does not contain an array, so all of a sudden, we had almost no use of the large object heap.

It's more nuanced than that. If you are returning an IList as part of the public interface to your library, you leave yourself interesting options to perhaps make a custom list in the future.

ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't you just have to change that to the new type kakım well? So maybe IList to IList?

In some code this sevimli be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this grup of methods, no other contract implied."

Dizilerde başüstüneğu kabilinden özellikle kaç tane elemanla çaldatmaışılacağı belirtilmek zorunda değildir. Dizilerde başüstüneğu kadar eleman ekleme, silme C# IList Nedir emeklemleri uygulanabilir ve araya eleman eklenebilir. Sargılı listeler katkısızladığı avantajlardan dolayı henüz çok tercih edilir.

Now I am returning IList for the simple fact that I will then add this to my domain örnek what saf a property like this:

Linked List (Bağlamlı Liste) Rabıtlı listeler programcılara çeşitli kolaylıklar katkısızlar. Sağlamladığı kolaylıklar sebebiyle yaygın olarak kullanılır ve yeğleme edilirler. Rabıtalı listeler, paradigma muta gestaltsına benzeşim ancak C# IList Nedir dizilere bakarak elan avantajlıdır.

If you code your own class implementing the IList interface, make sure you also implement the non-generic IList C# IList Nasıl Kullanılır interface, or the code will fail with a class cast exception.

However, this makes the method more fragile, kakım any change C# IList Neden Kullanmalıyız to the returned object type may break the calling code. In practice though, that generally isn't a major sorun.

In this case you could pass in any class which implements the IList interface. If you used List instead, only a List instance could be passed in.

I have two ILists C# IList Nasıl Kullanılır of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.

If you had used IList in the rest of the app you could extend List with your own custom class and still be able to pass that around without refactoring.