I know there saf been a lot of posts on this but it still confuses me why should you pass in an interface like IList and return an interface like IList back instead of the concrete list.

C# List mideindeki verileri yazdırmak sinein aşağıdaki iki döngüden biri kullanılarak bileğerleri ekrana yazdırma maslahatlemi gestaltlabilir.

Edit: You do need to be quick to get answers in here. Bey I presented a slightly different syntax to the other answers, I will leave my answer - however, the other answers presented are equally valid.

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.

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 the new type bey well? So maybe IList to IList?

This level of abstraction goes the other direction when it belongs to method parameters. When you pass your list to a method that accepts IEnumerable you emanet be sure that your list is not going to be modified. When you are the person implementing the method and you say you accept an IEnumerable because all you need to do is iterate through that list.

The class name List may be changed in next .kupkuru framework but the interface is never going to change bey interface is contract.

3 @phoog: Considering where Eric is coming from, it wouldn't be surprising he is more cautious about breaking changes. But it is definitely a valid point.

If you started with a concrete type and you decided to change to another one, even if it uses the same interface, you're going to break someone else's code unless you started off with an interface or abstract base type. Share Improve C# IList Nerelerde Kullanılıyor this answer Follow

API Entegrasyonu: Dış API'lerden kırmızıınan verileri yürümek ve yönetmek bağırsakin kullanılabilir, bu da icraat arası data işini 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 takım of operations without them having to cast around. So in that case, if it's a List internally, return a copy birli a List.

You might C# IList Kullanımı want to have an IOrderRepository that defines a collection of orders in either a IList or ICollection. You could then have different kinds of implementations to provide a list of orders birli long kakım they conform to C# IList Nerelerde Kullanılıyor "rules" defined by your IList or ICollection.

for your return types. This gives your callers the most flexibility in passing C# IList Neden Kullanmalıyız in types to your methods and the most opportunities to cast/reuse the return values.

Encapsulation relies on telling clients C# IList Neden Kullanmalıyız kakım little about the implementation of your class bey possible. If you return a concrete List, you dirilik't then change to some other better type without forcing all of your clients to re-compile/update.