The above is an IList itself bey this is what seems to be the standard to use with nhibernate. Otherwise I might have returned IEnumberable back but not sure. Still, I hayat't figure out what the user would 100% need(that's where returning a concrete has an advantage over).
From this it follows that your method implementation emanet represent its local variables however you wish. The implementation details are hamiş exposed. Leaving you free to change your code to something better without affecting the people calling your code.
If someone passes you an Array or a List, your code will work fine if you check the flag every time and have a fallback... But really; who does that?
Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.
Your code is now broken, because int[] implements IList, but is of fixed size. The contract for ICollection (the base of IList) requires the code that uses it to check the IsReadOnly flag before attempting to add or remove items from the collection. The contract for List does hamiş.
Architecture Astronauts. The chances you will ever write your own IList that adds anything to the ones already in the .Kemiksiz framework are so remote that it's theoretical jelly tots reserved for "best practices".
I thought I'd never need to change from a List but had to later change to use a custom list library for the extra functionality it provided. Because I'd only returned an IList none of the people that used the library had to change their code.
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 method, it güç 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 C# IList Nerelerde Kullanılıyor later if you decide to convert the actual data store from 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 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 birli an IEnumerable you emanet comfortably predict that your collection is derece being modified externally. That is one of the powers of exposing List C# IList Nasıl Kullanılır birli any of the above interfaces.
Süflidaki şekilde Kisi isminde C# IList Kullanımı oluşturduğumuz dershaneı oluşturduğumuz liste nesnesine ekleyelim.
Benefit of using an Interface is that you get to implement your functionality or better yet, the C# IList Nerelerde Kullanılıyor only functionality you require. So, if iteration/enumeration is required only, then there is no need for the Sort, Add methods.
When talking about return types, the more specific you are, the more flexible callers güç be with it.
Have children's car seats hamiş been proven to be more effective than seat belts alone C# IList Nasıl Kullanılır for kids older than 24 months?