The above is an IList itself kakım this is what seems to be the standard to use with nhibernate. Otherwise I might have returned IEnumberable back but hamiş sure. Still, I yaşama't figure out what the user would 100% need(that's where returning a concrete başmaklık an advantage over).
But far more importantly, if you are accepting an IList bey a parameter you'd better be careful, because IList and List do hamiş behave the same way. Despite the similarity in name, and despite sharing an interface
The less popular answer is programmers like to pretend their software is going to be re-used the world over, when infact the majority of projects will be maintained by a small amount of people and however birçok interface-related soundbites are, you're deluding yourself.
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
swilliamsswilliams 48.6k2727 gold badges101101 silver badges130130 bronze badges 3 5 why hamiş make it a just a List in the first place? I still don't understand why bonus you get from making it a IList then in the constructor you make it into a List
then, say, if you had an array and wished to print their type names to the console, you would first have to create a new List and fill it with your types.
List implements IList, and so gönül be assigned to the variable. There are also other types that also implement IList.
GitHub'da bizimle ortaklaşa iş binan Bu gönülğin kaynağı GitHub'da bulunabilir; burada hassaten problemlerı ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Elan zait selen muhtevain ulamada kâin kılavuzumuzu inceleyin.
In VS2008, when I click on the service reference and select "Configure Service Reference", there is an option to choose C# IList Nerelerde Kullanılıyor how the client bile-serializes lists returned from the service.
Then later if you decide to convert the actual veri store from a List to a Dictionary and expose the dictionary keys bey the actual value for the property (I have C# IList Neden Kullanmalıyız had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your C# IList Neden Kullanmalıyız class will no longer have that capability. That's a big sorun! If you expose the List kakım an IEnumerable you can comfortably predict that your collection is not being modified externally. C# IList Kullanımı That is one of the powers of exposing List as any of the above interfaces.
However, this makes the method more fragile, as any change to the returned object type may break the calling code. In practice though, that generally isn't a major sorun.
Returning a read-only interface such bey IEnumerable is often the way to go for data-retrieval methods. Your consumer emanet project it into a richer type as-needed.
If you use a concrete implementation of list, another implementation of the same list will not be supported by your code.
For instance, if you return an IEnumerable, then you are limiting them to iterating -- they can't add or remove items from your object, they sevimli only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you C# IList Kullanımı are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.