C# IList Neden Kullanmalıyız Seçenekler

C# IList Neden Kullanmalıyız Seçenekler

Blog Article

The above is an IList itself bey this is what seems to be the standard to use with nhibernate. Otherwise I might have returned IEnumberable back but derece sure. Still, I birey't figure out what the user would 100% need(that's where returning a concrete özgü an advantage over).

IList is an interface so you kişi inherit another class and still implement IList while inheriting List prevents you to do so.

Using IList instead of List makes writing unit tests significantly easier. It allows you to use a 'Mocking' library to pass and return data.

Birey a unique position be deduced if pieces are replaced by checkers (sevimli see piece color but not type)

The accepted answer by @DavidMills is quite good, but I think it sevimli be improved upon. For one, there is no need to define the ComparisonComparer class when the framework already includes a static method Comparer.Create(Comparison). This method can be used to create an IComparison on the fly.

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.

Most app-level code (i.e. the everyday code that ou write for your application) should probably focus on the generic versions; however there is also a lot of infrastructure code around that must use reflection.

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

And, if you don't even need everything in IList you gönül always use IEnumerable too. With çağcıl compilers and processors, I don't think there is really any speed difference, so this is more just a matter of style.

The Cast function is just a reimplementation of the C# IList Kullanımı extension method that comes with 3.5 written birli a olağan static method. It is quite ugly and verbose unfortunately.

Obviously if you are being asked which you use in an interview, you say IList, smile, and both look pleased C# IList Nerelerde Kullanılıyor at yourselves for being so clever. Or for a public facing API, IList. Hopefully you get my point.

You might want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then C# IList Kullanımı have different kinds of implementations to provide a list of orders birli long birli they conform to "rules" defined by your IList or ICollection.

for your return types. This gives your callers the most flexibility in passing in types to your methods and the most opportunities to cast/reuse the return values.

For instance, if you return an IEnumerable, C# IList Nedir then you are limiting them to iterating -- they güç't add or remove items from your object, they güç only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.