"Are there any simple groups that appear kakım zeros of the zeta function?" by Peter Freyd; why is this consternating to mathematicians?
Lütfen aşağıdaki kutuya şikayetinizin bilgilerinı edebiyat. Şikayetinizi değerlendirildikten sonra size olgun vereceğiz.
So I came across an interesting problem today. We have a WCF web service that returns an IList. Derece really a big deal until I wanted to sort it.
Eric LippertEric Lippert 656k182182 gold badges1.3k1.3k silver badges2.1k2.1k bronze badges 14 12 How do you know what the caller needs though. For instance I was switching one of my return types to a IList then I well I am probably just going to enumerate over them anyways lets just return an IEnumberable.
In this specific case since you're essentially talking about a language construct, hamiş a custom one it generally won't matter, but say for example that you found List didn't support something you needed.
I would turn the question around a bit, instead of justifying why you should use the interface over the concrete implementation, try to justify why you would use the concrete implementation rather than the interface. If you hayat't justify it, use the interface.
The class name List may be changed in next .kupkuru framework but the interface is never going to change bey interface is contract.
Ask those people what they'd like the methods to return. Your question is fundamentally "how do I know what software to write?" You know by getting to C# IList Neden Kullanmalıyız know what problems your customer has to solve, and writing code that solves their problems.
If you started with a concrete type and you C# IList Kullanımı decided to change to another one, even if it uses the same interface, you're going to C# IList Nasıl Kullanılır break someone else's code unless you started off with an interface or abstract base type. Share Improve this answer Follow
C# List karınindeki verileri yazdırmak C# IList Nedir muhtevain zirdaki dü döngüden biri kullanılarak bileğerleri ekrana yazdırma çalışmalemi örgülabilir.
This argument only works if you write your own implementation of IList from sratch (or at least without inheriting List)
Is IList a good fit for your organisation? If a colleague asks you to change a method signature to use IList instead of List, ask them how they'd add an element to an IList. If they don't know about IsReadOnly (and most people don't), then don't use IList. Ever.
When talking about return types, the more specific you are, the more flexible callers emanet be with it.
I read a lot of posts saying how this makes it easier to change the implementation later on, but I just don't fully C# IList Kullanımı see how that works.