En iyi Tarafı C# IList Kullanımı

En iyi Tarafı C# IList Kullanımı

Blog Article

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.

But far more importantly, if you are accepting an IList kakım a parameter you'd better be careful, because IList and List do not behave the same way. Despite the similarity in name, and despite sharing an interface

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.

David MillsDavid Mills 2,41511 gold badge2323 silver badges2525 bronze badges 6 2 The right approach really would have been to offer an ISortableList interface (with methods to sort a portion of the list using some particular comparer), have List implement it, and have a static method which could sort any IList by checking whether it implemented ISortableList and, if hamiş, copying it to an array, sorting that, clearing the IList, and re-adding the items.

This will allow me to do generic processing on almost any array in the .Safi framework, unless it uses IEnumerable and derece IList, which happens sometimes.

Architecture Astronauts. The chances you will ever write your own C# IList Neden Kullanmalıyız IList that adds anything to the ones already in the .Kemiksiz framework are so remote that it's theoretical jelly tots reserved for "best practices".

use LINQ to perform the conversion of your existing List when you return it - but it would be better to just create a more appropriate type to start with, kakım shown above.

Matthew WatsonMatthew Watson 108k1111 gold badges170170 silver badges290290 bronze badges 2 2 This is trivially true for every interface. If you want to follow through with your argument, than you could argue to never use any interface at C# IList Neden Kullanmalıyız all, because some implementation of it might throw.

Whether you return an Interface or a concrete type depends upon what you want to let your callers do with the object you created -- this is an API design C# IList Nasıl Kullanılır decision, and there's no hard and fast rule. C# IList Nedir You have to weigh their ability to make full use of the object against their ability to easily use a C# IList Nerelerde Kullanılıyor portion of the objects functionality (and of course whether you WANT them to be making full use of the object).

C# List karınindeki verileri yazdırmak ciğerin kötüdaki iki döngüden biri kullanılarak değerleri ekrana yazdırma davranışlemi mimarilabilir.

IList.IsFixedSize bileğerinin mıhlı bir boyuta sahip olup olmadığını IList belirten bir paha allıkır.

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.

So typically, your methods should accept and return interfaces for collections. This leaves your own implementation and your callers room to decide on the actual implementation kakım required.

Have children's car seats not been proven to be more effective than seat belts alone for kids older than 24 months?