How to refer to the locations in lower depths of a waterbody (such birli a lake)? more hot questions
Bayağıdaki şekilde Kisi adında oluşturduğumuz dershaneı oluşturduğumuz liste nesnesine ekleyelim.
lomaxxlomaxx 115k5858 gold badges146146 silver badges180180 bronze badges 1 Why would you return an IList in the first place? From a WCF service?
Sıfır zir hatına sahip uslu boyutlu diziler otomatik olarak uygular IList. Bu, diziler ve gayrı derme türleri beyninde yineleme geçirmek derunin aynı kodu kullanabilen umumi yöntemler oluşturmanıza olanak teşhisr.
The accepted answer by @DavidMills is quite good, but I think it güç 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 yaşama be used to create an IComparison on the fly.
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 yaşama't justify it, use the interface.
+1 for all of us who hate it when a small app is loaded with interfaces and clicking on "find definition" takes us somewhere OTHER than the source of the sorun... Dirilik I borrow the phrase "Architecture Astronauts"? I gönül see it will come in handy.
Now I am returning IList for the simple fact that I will then add this to my domain mostra what başmaklık a property like this:
In most cases, if you are using a List and you think you could use a narrower interface instead - why derece IEnumerable? This is often a better fit if you don't need to add items. If you need to add to the collection, use the concrete type, List.
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 C# IList Nerelerde Kullanılıyor breaking other people's code, then go more general.
Of course that only need apply to methods that are externally visible (i.e. public methods). I personally use interfaces even in internal code, but as you are able to change all the code yourself if you make breaking changes it's not strictly necessary.
Collaborate with us on GitHub The source for this content hayat be found C# IList Nerelerde Kullanılıyor on GitHub, where you hayat also create and review issues and pull requests. For more information, see our contributor guide.
Unless you have a very compelling reason to C# IList Nedir do so, your best bet will be to inherit from System.Collections.ObjectModel.Collection since it katışıksız everything you need.
ahead of time. Data-binding is a classic example here; a C# IList Nedir DataSource property usually checks for IList (and IListSource, typically) and then looks at the objects to see what C# IList Neden Kullanmalıyız properties are available. It birey't use generics in this case.