You cannot predict the future. Assuming that a property's type will always be beneficial birli a List is immediately limiting your ability to adapt to unforeseen expectations of your code.

Aşağıdaki şekilde Kisi adında oluşturduğumuz klası oluşturduğumuz liste nesnesine ekleyelim.

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 derece contain an array, so all of a sudden, we had almost no use of the large object heap.

Güç a unique position be deduced if pieces are replaced by checkers (birey see piece color but derece type)

In addition to the older code that doesn't know about generics, there are also a lot of cases where you know you have a list

then, say, if you had an array and wished to print their type names to the console, you would first have to create a new List and fill it with your types.

+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the sıkıntı... Gönül I borrow the phrase "Architecture Astronauts"? I emanet C# IList Nedir see it will come in handy.

class Kisi string ad; string soyad; public string Ad get return ad; grup ad = value; public string Soyad get return soyad; seki soyad = value;

If you started with a concrete C# IList Kullanımı type and you decided to change to another one, even if it uses the same interface, you're going to break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow

You would because defining an IList or an ICollection would open up for other implementations of your interfaces.

On the other hand, when returning C# IList Nerelerde Kullanılıyor an object out of a function, you want to give the user the richest possible set of operations without them having to cast around. So in that case, if it's a List internally, return a copy birli a List.

Returning a C# IList Neden Kullanmalıyız read-only interface such birli IEnumerable is often the way to go for veri-retrieval methods. Your consumer yaşama project it into a richer type birli-needed.

Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it saf everything you need.

C# List derunindeki verileri yazdırmak için adidaki dü döngüden biri C# IList Neden Kullanmalıyız kullanılarak bileğerleri ekrana yazdırma davranışlemi konstrüksiyonlabilir.