It's always best to use the lowest base type possible. This gives the implementer of your interface, or consumer of your method, the opportunity to use whatever they like behind the scenes.
Same principle bey before, reversed. Offer the bare minimal that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
So I came across an interesting sorun today. We have a WCF web service that returns an IList. Derece really a big deal until I wanted to sort it.
Kendi derme sınıflarınızı oluştururken tekrar kullanılabilir harf yazmanızı sağlar: C# CollectionBase kullanarak genel koleksiyon işlemlemlerini dâhileren bir kök dershane oluşturabilirsiniz.
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 derece.
Örneğin, zirdaki kodda bir IAnimal tipinde bir değişken teşhismladım ve bu değdavranışkene Dog ve Cat nesneleri atadım.
You are most often better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you emanet switch the implementation conveniently at a later time.
Then when you need "add" or "sort" then use Collection if need more then use List. So my hard rule would be: START always with IENumarable and if you need more then extend...
In VS2008, when I click on the service C# IList Nedir reference and select "Configure Service Reference", there is an option to choose how the client bile-serializes lists returned from the service.
The Cast function is just a reimplementation of the extension method that comes with 3.5 written bey a normal static method. It is quite ugly and verbose unfortunately.
On the other hand, when returning an object out of a function, you want to give the user the richest possible grup of operations without C# IList Neden Kullanmalıyız them having to cast around. So in that case, if it's a List internally, return a copy as a List.
Returning a read-only interface such as IEnumerable is often the way to go for veri-retrieval methods. Your consumer emanet project it into C# IList Nedir a richer type kakım-needed.
You accept an Interface kakım a parameter for a method because that allows C# IList Nasıl Kullanılır the caller to submit different concrete types as arguments. Given your example method LogAllChecked, the parameter someClasses could be of various types, and for C# IList Nedir the person writing
would I run into problems with this? Since could they hamiş pass in an array(that saf a fixed size)? Would it be better maybe for a concrete List?