Else use List. You güç'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"
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government?
Bir dahaki sefere değerlendirme yapmış olduğumda kullanılmak üzere etapı, elektronik posta adresimi ve web kent adresimi bu tarayıcıya kaydet.
That way you take advantage if you kişi, while still allowing the client flexibility in what they pass in.
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.
In some code this güç be quite important and using concrete classes communicates your intent, your need for that specific class. An interface on the other hand says "I just need to call this seki of methods, no other contract implied."
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the problem... Can I borrow the phrase "Architecture Astronauts"? I kişi see it will come in handy.
IList is an Interface, derece a class. If you want to initialize it, you need to initialize it to a class that implements C# IList Nedir IList, depending on your specific needs internally. Usually, IList is initialized with a List.
One Piece Şeytan Meyveleri Kitabı ile anime yazılarımıza devam edelim. Önceleri toparladığım bir tasarydı bu yazı. Bir anime izlerken o animeyi ne derece çok sevdiğime…
Modülerlik: Yazılı sınavm projelerinde modüler bir yaklaşım sunarak harf yenidenını azaltır ve hizmetı kolaylaştırır.
On the other hand, when returning an object out of a function, you want to give the user the richest possible kaş of operations without them having to cast around. C# IList Nasıl Kullanılır So in that case, if it's a List internally, return a copy kakım a List.
This is usually guaranteed for a specific implementation of a container (List documentation: "It implements the IList generic interface using an array whose size is dynamically increased as required.").
You accept an C# IList Nasıl Kullanılır Interface birli a parameter for a method because C# IList Nerelerde Kullanılıyor that allows the caller to submit different concrete types bey arguments. Given your example method LogAllChecked, the parameter someClasses C# IList Nerelerde Kullanılıyor could be of various types, and for the person writing
additional advantage is that your code is safe from any changes to concrete class bey you are subscribing to only few of the methods of concrete class and those are the ones that are going to be there bey long bey the concrete class inherits from the interface you are using.