You cannot predict the future. Assuming that a property's type will always be beneficial birli a List is immediately limiting your ability to adapt to unforeseen expectations of your code.
Then the person calling the method is free to call it with any data type that is enumerable. This allows your code to be used in unexpected, but perfectly valid ways.
Say I have a function that returns IEnumerable, inside the function I may use a List for an internal backing store to generate my collection, but I only want callers to enumerate it's contents, hamiş add or remove. Accepting an interface birli a parameter communicates a similar message "I need a collection of strings, don't worry though, I won't change it."
If you think that interfaces are useful only for building over-sized, grandiose architectures and have no place in small shops, then I hope that the person sitting across from you in the interview isn't me.
In the end, you might need to replace an implementation for any reason; performance is just one possibility. Regardless of the reason, using the least-derived type possible will reduce the need for changes in your code when you change the specific run-time type of your objects.
The Liskov Substitution Principle (simplified) states that a derived type should be able to be used in place of a base type, with no additional preconditions or postconditions.
You are most often C# IList Neden Kullanmalıyız better of using the most general usable type, in this case the IList or even better the IEnumerable interface, so that you can switch C# IList Nedir the implementation conveniently at a later time.
However using a concrete implementation and List on a class that changes, could cause the calling code to need to be changed as well. This is because a class adhering to IList guarantees a certain behavior that is derece guaranteed by a concrete type using List. C# IList Nasıl Kullanılır Also having the power to do something C# IList Neden Kullanmalıyız like modify the default implementation of List on a class Implementing IList for say the .Add, .Remove or any other IList method gives the developer a lot
Whether you return an C# IList Neden Kullanmalıyız Interface or a concrete type depends upon what you want to let your callers do with the object you created -- this is an API design decision, and there's no hard and fast rule. You have to weigh their ability to make full use of the object against their ability to easily use a portion of the objects functionality (and of course whether you WANT them to be making full use of the object).
Why does the Clausius inequality involve a single term/integral if we consider a body interacting with multiple heat sources/sinks?
On the other hand, when returning an object out of a function, you want to give the user the richest possible set of operations without 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 bey IEnumerable is often the way to go for veri-retrieval methods. Your consumer yaşama project it into a richer type as-needed.
Unless you have a very compelling reason to do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it katışıksız everything you need.
Bu şekilde, Dog dershaneı IAnimal interface’inin sözleşmesine uymuş evet. Aynı şekilde, başka efsanevi sınıfları da IAnimal interface’ini uygulayabilir. Örneğin, bayağıdaki kodda bir Cat sınıfı tanımladım ve IAnimal interface’ini uyguladım.