En iyi Tarafı C# IList Nedir

En iyi Tarafı C# IList Nedir

Blog Article

driisdriis 163k4545 gold badges268268 silver badges343343 bronze badges 3 Sorry, but even now there are plenty of uses for library code to use IList (non-generic). Anyone who says otherwise hasn't suffered enough reflection / veri-binding / etc ;)

From this it follows that your method implementation birey represent its local variables however you wish. The implementation details are not exposed. Leaving you free to change your code to something better without affecting the people calling your code.

Edit: You do need to be quick to get answers in here. Kakım I presented a slightly different syntax to the other answers, I will leave my answer - however, the other answers presented are equally valid.

So when writing a function or method that takes a collection, write it derece to take a List, but an IList, an ICollection, or IEnumerable. The generic interfaces will still work even for heterogenous lists because System.

Use whatever you want. It's your method. You're the only one who gets to see the internal implementation details of the method.

Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

StuartLCStuartLC 106k1818 gold badges216216 silver badges289289 bronze badges Add a comment  

However using a concrete implementation and List on a class that changes, could cause the calling code to need to be changed bey well. This is because a class adhering to IList guarantees a certain behavior that is derece guaranteed by a concrete type using List. Also having the power to do C# IList Nerelerde Kullanılıyor 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

the method, it sevimli make a huge difference -- if they have an array and you're asking for a list, they have to change the array to a list or v.v. whenever calling the method, a total waste of time from both a programmer and performance POV.

Then later if you decide to convert the actual veri store from C# IList Kullanımı a List to a Dictionary and expose the dictionary keys as the actual value for the property (I have had to do exactly this before). Then consumers who have C# IList Nasıl Kullanılır come to expect that their changes will be reflected inside of your class will no longer have that capability. That's a big problem! If you expose the List C# IList Nerelerde Kullanılıyor as an IEnumerable you gönül comfortably predict that your collection is not being modified externally. That is one of C# IList Kullanımı the powers of exposing List bey any of the above interfaces.

 

Returning a read-only interface such birli IEnumerable is often the way to go for data-retrieval methods. Your consumer emanet project it into a richer type birli-needed.

You can pass a plain array to something which accepts an IList parameter, and then you sevimli call IList.Add() and will receive a runtime exception:

There is a complication though that dynamic dirilik't see explicit implementations, so something hayat implement IList and IList-of-T and yet still be completely unusable from dynamic.