We needed the list indexer infrequently, so the inefficiency was hamiş a problem. If it had been, we could have provided some other implementation of IList, perhaps as a collection of small-enough arrays, that would have been more efficiently indexable while also avoiding large objects.
But far more importantly, if you are accepting an IList birli a parameter you'd better be careful, because IList and List do hamiş behave the same way. Despite the similarity in name, and despite sharing an interface
You pass the interface so that no matter what concrete implementation of that interface you use, your code will support it.
Sıfır zir hudutına iye biricik boyutlu diziler otomatik olarak uygular IList. Bu, diziler ve özge derlem türleri arasında yineleme yapmak dâhilin aynı kodu kullanabilen umumi yöntemler oluşturmanıza olanak tanılamar.
In this specific case since you're essentially talking about a language construct, not a custom one it generally won't matter, but say for example that you found List didn't support something you needed.
IList on the other hand is an Interface. Basically, if you want to create your own custom List, say a list class called BookList, then you emanet use the Interface to give you basic methods and structure to your new class. IList is for when C# IList Nasıl Kullanılır you want to create your own, special sub-class that implements List.
StuartLCStuartLC 106k1818 gold badges216216 silver badges289289 bronze badges Add a comment
However using a concrete implementation C# IList Nedir and List on a class that changes, could cause the calling code to need to be changed as well. This is because a class adhering C# IList Nedir to IList guarantees a certain behavior that is hamiş guaranteed by a concrete type using List. Also having the C# IList Kullanımı power to do something like modify the default implementation of List on a class Implementing IList for say the .Add, .Remove or any other IList method gives the developer a lot
Linked List (Sargılı Liste) Sargılı listeler programcılara çeşitli kolaylıklar sağlamlar. Sağladığı kolaylıklar sayesinde münteşir olarak kullanılır ve tercih edilirler. Bentlı listeler, dizi data yapısına model ancak dizilere göre daha avantajlıdır.
You would because defining an IList or an ICollection would open up for other implementations of your interfaces.
Obviously if you are being asked which you use in an interview, you say IList, smile, and both look pleased at yourselves for being so clever. Or for a public facing API, IList. Hopefully you get my point.
Şimdi bu arada bir örnek yapalım. Bir tenha yönlü destelı liste oluşturalım ve bu listeye herhangi olarak eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:
If you use a concrete implementation of list, another implementation of the same list will hamiş be supported by your code.
Have C# IList Nasıl Kullanılır children's car seats hamiş been proven to be more effective than seat belts alone for kids older than 24 months?