Benim C# IList Neden Kullanmalıyız Başlarken Çalışmak

Benim C# IList Neden Kullanmalıyız Başlarken Çalışmak

Blog Article

I know there özgü 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.

Başarım Optimizasyonu: IList, muta erişimini optimize ederek uygulamanın başarımını zaitrabilir ve dağarcık yönetimini iyileştirebilir.

lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?

Kendi koleksiyon sınıflarınızı oluştururken yine kullanılabilir harf yazmanızı sağlamlar: C# CollectionBase kullanarak umumi koleksiyon emeklemlerini yürekaziz bir omurga klas oluşturabilirsiniz.

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.

Yes, you may never change that veri type from a List but you dirilik be sure that if you have to. Your code is ready for it.

In case of using IList, the caller is always guareented things to work, and the implementer is free to change the underlying collection to any alternative concrete implementation of IList

If your methods form part of an interface, the methods will need to be defined using types available to that interface.

For collections you should aim to use IEnumerable C# IList Nasıl Kullanılır where possible. This gives the most flexibility but is hamiş always suited.

What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government? more hot questions

This argument only C# IList Nasıl Kullanılır works if you write your own implementation of IList from sratch (or at least without inheriting List)

Less ridiculous way C# IList Nasıl Kullanılır to prove that an Ascii character compares equal with itself in Coq more hot C# IList Nedir questions

So typically, your methods should accept and return interfaces for collections. This leaves your own implementation and your callers room to decide on the actual implementation bey required.

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