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.
Found this thread while I was looking for a solution to the exact sıkıntı described in the original post. None of the answers met my situation entirely, however. Brody's answer was pretty close. Here is my situation and solution I found to it.
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.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
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.
IList on the other hand is an Interface. Basically, if you want to create your own custom List, say a list class called BookList, then you birey use the Interface to give you basic methods and structure to your new class. IList is for when you want to create your own, special sub-class that implements List.
class Kisi string ad; string soyad; public string Ad get return ad; seki ad = value; public string Soyad get return soyad; set soyad = C# IList Nasıl Kullanılır value;
Now I am returning IList for the simple fact that I will then add this to my domain model what has a property like this:
the method, it C# IList Neden Kullanmalıyız can 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 C# IList Kullanımı calling the method, a total waste of time from both a programmer and performance POV.
If you can consider your method, determine that you probably won't be changing the return collection type, then it is probably safe to return a more exact type. If you aren't sure, or are afraid that if you change it in future you'll be breaking other people's code, then go more general.
Of course that only need apply to methods that are externally visible (i.e. public methods). I personally use C# IList Neden Kullanmalıyız interfaces even in internal code, but bey you are able to change all the code yourself if you make breaking changes it's not strictly necessary.
You might want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders birli long bey they conform to "rules" defined by your IList or ICollection.
You sevimli pass a plain array to something which accepts an IList parameter, and then you güç call IList.Add() and will receive a runtime exception:
There is a complication though that dynamic dirilik't see explicit implementations, so something can implement IList and IList-of-T and yet still C# IList Kullanımı be completely unusable from dynamic.