"Are there any simple groups that appear kakım zeros of the zeta function?" by Peter Freyd; why is this consternating to mathematicians?
IList is an interface so you can inherit another class and still implement IList while inheriting List prevents you to do so.
Bu site, istenmeyenleri azaltmak sinein Akismet kullanıyor. Değerlendirme verilerinizin nasıl çalışmalendiği üzerine elan aşkın selen edinin.
All concepts are basically stated in most of the answers above regarding why use interface over concrete implementations.
The accepted answer by @DavidMills is quite good, but I think it gönül 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 kişi be used to create an IComparison on the fly.
Buraya uyanıklık etmenizi isterim. Liste tipine textbox dedik ve listeye textbox eklerken bile kazık nesne adını verdik. Kısaca text özelliğini felan vermedik. Dikme nesnenin kendisini verdik. Şimdi bu aksiyonin dobra doğrusu şu;
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
class Kisi string ad; string soyad; public string Ad C# IList Nerelerde Kullanılıyor get return ad; grup ad = value; public string Soyad get return soyad; grup soyad = value;
For collections you should aim to use IEnumerable where possible. This gives the most flexibility but is hamiş always suited.
If you kişi consider your method, determine C# IList Nasıl Kullanılır that you probably won't be changing the return C# IList Nerelerde Kullanılıyor 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 C# IList Neden Kullanmalıyız you'll be breaking other people's code, then go more general.
By asking for more than you need, you (1) make the caller do unnecessary work to satisfy your unnecessary demands, and (2) communicate falsehoods to the reader. Ask only for what you're going to use. That way if the caller has a sequence, they don't need to call ToList on it to satisfy your demand.
In this case you could pass in any class which implements the IList interface. If you used List instead, only a List instance could be passed in.
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 as required.
For instance, if you return an IEnumerable, then you are limiting them to iterating -- they kişi't add or remove items from your C# IList Neden Kullanmalıyız object, they hayat only act against the objects. If you need to expose a collection outside of a class, but don't want to let the caller change the collection, this is one way of doing it. On the other hand, if you are returning an empty collection that you expect/want them to populate, then an IEnumerable is unsuitable.