5 Basit Teknikleri için C# IList Nedir

5 Basit Teknikleri için C# IList Nedir

Blog Article

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

Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.

So I came across an interesting problem today. We have a WCF web service that returns an IList. Derece really a big deal until I wanted to sort it.

That way you take advantage if you gönül, while still allowing the client flexibility in what they pass in.

I tend to follow Jeffrey's advice for internal code, but for a public library, I would probably be more inclined to follow Eric's.

You birey have an instance of an interface, but you need to initialize it with a class that implements that interface such bey:

Inside the method, you should use var, instead of IList or List. When your veri source changes to come from a method C# IList Nedir instead, your onlySomeInts method will survive.

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

The idea is that you C# IList Nerelerde Kullanılıyor hide the implementation details from the user, and instead provide them with a stable interface. This is to reduce dependency on details that might change in the future.

If you güç consider your method, determine that you probably won't be changing the return collection C# IList Neden Kullanmalıyız type, then it is probably safe to return a more exact type. If you aren't sure, or are afraid that if C# IList Kullanımı you change it in future you'll be breaking other people's code, then go more general.

However, this makes the method more fragile, kakım C# IList Neden Kullanmalıyız any change to the returned object type may break the calling code. In practice though, that generally isn't a major mesele.

List communicates "I need to get and grup the elements of this sequence in arbitrary order and I only accept lists; I do derece accept arrays."

When talking about return types, the more specific you are, the more flexible callers birey be with it.

ahead of time. Data-binding is a classic example here; a DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what properties are available. It emanet't use generics in this case.