Bir İnceleme C# IList Neden Kullanmalıyız

Wiki Article

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

Performans Optimizasyonu: IList, done erişimini optimize ederek uygulamanın başarımını fazlalıkrabilir ve bellek yönetimini iyileştirebilir.

Interface’ler üzerine elan bir tomar bili peyda etmek isterseniz, aşağıdaki kaynaklara dide atabilirsiniz:

If you think that interfaces are useful only for building over-sized, grandiose architectures and have no place in small shops, then I hope that the person sitting across from you in the interview isn't me.

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

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.

+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ı... Can I borrow the phrase "Architecture Astronauts"? I can see it will come in handy.

Don't you know in advance if your method needs a list that sevimli take additional members; C# IList Nerelerde Kullanılıyor don't you specify that in the method signature? What exactly were you going to C# IList Neden Kullanmalıyız do if you were passed a read only list like int[]?

If you are exposing C# IList Nasıl Kullanılır your class through a library that others will use, you generally want to expose it via interfaces rather than concrete C# IList Neden Kullanmalıyız implementations.

If you code your own class implementing the IList interface, make sure you also implement the non-generic IList interface, or the code will fail with a class cast exception.

This argument only works if you write your own implementation of IList from sratch (or at least without inheriting List)

Is IList a good fit for your organisation? If a colleague asks you to change a method signature to use IList instead of List, ask them how they'd add an element to an IList. If they don't know about IsReadOnly (and most people C# IList Nedir don't), then don't use IList. Ever.

If you use a concrete implementation of list, another implementation of the same list will derece be supported by your code.

It doesn't affect the signature of the method, and is takım in stone at compile time. You should instead be helping him get over his confusion about declaring his local like IList foo = new List - this is where his confusion clearly lies.