şu demek oluyor ki IEnumerable mimarisında filtreleme konulemleri memory bile bünyelırken, IQueryable da veritabanından direk filtrelenmiş verileri elde ederiz.
Bir dahaki sefere yorum yapmış olduğumda kullanılmak üzere etapı, e-posta adresimi ve web kent adresimi bu tarayıcıya kaydet.
The less popular answer is programmers like to pretend their software is going to be re-used the world over, when infact the majority of projects will be maintained by a small amount of people and however nice interface-related soundbites are, you're deluding yourself.
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.
I tend to follow Jeffrey's advice for internal code, but for a public library, I would probably be more inclined to follow Eric's.
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 güç't justify it, use the interface.
Most app-level code (i.e. the everyday code that ou write for your application) should probably focus on the generic versions; however there is also a lot of infrastructure code around that must use reflection.
If your methods form part of an interface, the methods will need to be defined using types available to that interface.
For example, let's say you have a Person class and a Group class. A Group instance saf many people, so a C# IList Nasıl Kullanılır List here would make sense. When I declare the list object in Group I will use an IList and instantiate it birli a C# IList Neden Kullanmalıyız List.
Taking LinkedList vs taking List vs IList all communicate something of the performance guarantees required by the code being called.
IList.IsFixedSize bileğerinin sabit bir C# IList Neden Kullanmalıyız boyuta sahip olup olmadığını IList belirten bir şayan allıkır.
Then I looked in my view(mvc) and found that I actually needed the count method C# IList Nerelerde Kullanılıyor as I needed to use a for loop. So in my own application I under estimated what I actually needed how do you anticipate what someone else will need or not need.
List sınıfı teşhismlanırken T tip değaksiyonkenini alır. şu demek oluyor ki listenin içeriğinde ne türden nesne yada değmeselekenlerin olacağını belirler.
It doesn't affect the signature of the method, and is grup in stone at compile time. You should instead be helping him get over his confusion about declaring his local like IList foo C# IList Neden Kullanmalıyız = new List - this is where his confusion clearly lies.