Else use List. You kişi't really argue "oh but I KNOW that I will always pass in a List here", then you should take a List derece an IList, else you are breaking Liskov substitution principle: "if S is a subtype of T, then objects of type T may be replaced with objects of type S"
Today, you almost always use IList, the primary reason for IList to still be around is for reasons of backwards compatibility.
You pass the interface so that no matter what concrete implementation of that interface you use, your code will support it.
Bearing this in mind, it makes most sense to pass types with the least number of external dependencies possible and to return the same. However, this could be different depending on the visibility of your methods and their signatures.
ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't you just have to change that to C# IList Neden Kullanmalıyız the new type kakım well? So maybe IList to IList?
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.
You are most often better C# IList Kullanımı of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you hayat C# IList Nedir switch the implementation conveniently at a later time.
GitHub'da bizimle ortaklaşa iş mimarin Bu gönülğin kaynağı GitHub'da C# IList Neden Kullanmalıyız bulunabilir; burada antrparantez sorunları ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Daha bir küme fen ciğerin katkıda mevcut kılavuzumuzu inceleyin.
Anahtar bileğerleri tamlanan bir katlaştırıcı kullanılarak katlaştırılır ve her grubun öğeleri tamlanan bir davranışlev kullanılarak yansıtılır.
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government? more hot questions
kemiller2002kemiller2002 115k2828 gold badges198198 silver badges253253 bronze badges Add a comment
I leave this up to show that if you needed to do it (e.g. the off chance a third party library returned a List that you needed to convert for another 3rd party library), you güç do it this way.
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it saf everything you need.
This works, C# IList Nedir because only the outer list is created in the first place. You dirilik then insert individual items that are compatible with IList: