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 bey a List is immediately limiting your ability to adapt to unforeseen expectations of your code.

What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government?

Also, it casts IList to IList which başmaklık the potential to be dangerous. In most cases that I have seen, List which implements IList is used behind the scenes to implement IList, but this is derece guaranteed and dirilik lead to brittle code.

Then click on the bulb symbol or place the cursor on the IList and press Strg + "." You will become several implementations offered, like:

In the end, you might need to replace an implementation for any reason; performance is just one possibility. Regardless of the reason, using the least-derived type possible will reduce the need for changes in your code when you change the specific run-time type of your objects.

Convert your IList into List or some other generic collection and then you güç easily query/sort it using System.Linq namespace (it will supply bunch of extension methods)

You may derece ever need that option, but it's an argument. I think it's the entire argument for returning the interface instead of the concrete type. It's worth mentioning, but C# IList Kullanımı in this case it has a serious flaw.

 

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 C# IList Nerelerde Kullanılıyor design decision, and there's no hard and fast rule. You have to weigh their ability to make full use of the object against their ability to easily use a portion of the objects functionality (and of course whether you WANT them to be making full use of the C# IList Neden Kullanmalıyız object).

The Cast function is just a reimplementation of the extension method that comes with 3.5 written birli a uygun static method. It is quite ugly and verbose unfortunately.

If you're working within a single method (or even C# IList Neden Kullanmalıyız in a single class or assembly in some cases) and no one outside is going to see what you're doing, use the fullness of a List. But if you're interacting with outside code, like when you're returning C# IList Kullanımı a list from a method, then you only want to declare the interface without necessarily tying yourself to a specific implementation, especially if you have no control over who compiles against your code afterward.

Brad LeachBrad Leach 17k1818 gold badges7373 silver badges8888 bronze badges 1 3 It will create a new enumerable, which may not be desirable in some scenarios. You cannot sort an IList in-place through the interface except by using ArrayList.Adapter method in my knowledge.

I have two ILists of the same type returned by NHibernate and have emerged the two IList into one, hence the need for sorting.

If you had used IList in the rest of the app you could extend List with your own custom class and still be able to pass that around without refactoring.