"Are there any simple groups that appear as zeros of the zeta function?" by Peter Freyd; why is this consternating to mathematicians?
Arec BarrwinArec Barrwin 61.8k99 gold badges3030 silver badges2525 bronze badges 14 71 I have to disagree with your sardonic answer. I don't totally disagree with the sentiment of over-architecture being a real problem. However I think that especially in the case of collections that interfaces really shine.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
Your functions above only care about being able to iterate over a list. Ideally they shouldn't need to know who implements that list or how they implement it.
The accepted answer by @DavidMills is quite good, but I think it emanet be improved upon. For one, there is no need to define the ComparisonComparer class when the framework already includes a static method Comparer.Create(Comparison). This method güç be used to create an IComparison on the fly.
Important Some C# IList Nasıl Kullanılır information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes C# IList Nasıl Kullanılır no warranties, express or implied, with respect to the information provided here.
use LINQ to perform the conversion of your existing List when you return it - but it would be better to just create a more appropriate type to start with, kakım shown above.
If C# IList Nasıl Kullanılır the collection is indexed, the indexes of the elements that are moved are also updated. This behavior does hamiş apply to collections where elements are conceptually grouped into buckets, such bey a hash table.
For collections you should aim to use IEnumerable where possible. This gives the most flexibility but is not always suited.
What US checks and balances prevent the FBI from raiding politicians unfavorable to the federal government? more hot questions
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 C# IList Kullanımı don't know about IsReadOnly (and most people don't), then don't use IList. Ever.
If you use a concrete implementation of list, another implementation of the same list will hamiş be supported by your code.
Encapsulation relies on telling clients kakım little about the implementation of your class C# IList Neden Kullanmalıyız bey possible. If you return a concrete List, you emanet't then change to some other better type without forcing all of your clients to re-compile/update.