I know there katışıksız 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.

Performans Optimizasyonu: IList, bilgi erişimini optimize ederek uygulamanın performansını artırabilir ve akıl yönetimini iyileştirebilir.

Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.

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.

swilliamsswilliams 48.6k2727 gold badges101101 silver badges130130 bronze badges 3 5 why derece make it a just a List in the first place? I still don't understand why bonus you get from making it a IList then in the constructor you make it into a List

so its safety for you and freedom to the coder who is writing concrete implementation to change or add more functionality to his concrete class.

 

However using a concrete implementation and List on a class that changes, could cause the calling code to need to be changed kakım well. This is because a class adhering to IList guarantees a certain behavior that is hamiş guaranteed by a concrete type C# IList Nerelerde Kullanılıyor using List. Also having the power to do something 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

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 this answer Follow

If you birey consider your method, determine that you probably won't be changing the return collection type, then it is probably safe to return a more exact type. If you aren't sure, or are afraid that if you change it in future you'll be breaking other people's code, C# IList Nerelerde Kullanılıyor then go more general.

Dirilik you please provide me some link to a class that implements IList interface or provide me a code that at least implements Add and Remove methods?

Şimdi beraber bir örnek yapalım. Bir tek yönlü bağlamlı liste oluşturalım ve bu listeye herhangi olarak C# IList Neden Kullanmalıyız eleman ekleyelim. Bu eklediğimiz elemanları da ekrana yazdıralım:

This will help if you decide to change the implementation of your class later to use a different concrete class. In C# IList Neden Kullanmalıyız that case the users of your library won't need to update their code since the interface doesn't change.

Encapsulation relies on telling clients bey little about the implementation C# IList Nerelerde Kullanılıyor of your class as possible. If you return a concrete List, you can't then change to some other better type without forcing all of your clients to re-compile/update.