şu demek oluyor ki IEnumerable yapısında filtreleme teamüllemleri memory de kuruluşlırken, IQueryable da veritabanından direk filtrelenmiş verileri elde ederiz.
Same principle kakım before, reversed. Offer the bare minimal that your caller requires. If the caller only requires the ability to enumerate the sequence, only give them an IEnumerable.
Interface’ler için henüz okkalı marifet edinmek isterseniz, kötüdaki kaynaklara delik atabilirsiniz:
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.
ToList first? How about returning it? I don't understand what you mean by "method will survive" when using vars? I know it will be a bit more work but won't you just have to change that to the new type as well? So maybe IList to IList?
Örneğin, zirdaki kodda bir IAnimal tipinde bir mütehavvil teşhismladım ve bu değemekkene Dog ve Cat nesneleri atadım.
StuartLCStuartLC 106k1818 gold badges216216 silver badges289289 bronze badges Add a comment
In fact, any time you are using reflection IList is more convenient than IList-of-T, since generics and reflection don't play nicely together. It dirilik be done, but it is a pain. Unfortunately since IList-of-T doesn't derive from IList there are cases where this gönül yapan - but it is a good 95% rule.
In most cases, if you are using a List and you think you could use a narrower interface instead - why not IEnumerable? This C# IList Nasıl Kullanılır 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.
Then later if you decide to convert C# IList Nedir the actual veri store from a List to a Dictionary and expose the dictionary keys kakım the actual value for the property (I have had to do exactly this before). Then consumers who have come to expect that their changes will be reflected inside of your class will no longer have that capability. That's a big sıkıntı! If you expose the List bey an IEnumerable you gönül comfortably predict that your collection is not being modified externally. That is one of the powers of exposing List kakım any of the above interfaces.
However, this makes the method more fragile, kakım any change to the returned object type may break the calling code. In practice though, that generally isn't a major sıkıntı.
Brad LeachBrad Leach 17k1818 gold badges7373 silver badges8888 bronze badges 1 3 It will create a new enumerable, which may not be desirable in some scenarios. You cannot sort an IList in-place through the interface except by using ArrayList.Adapter method in my knowledge.
If you're just enumerating over the values, you should be using IEnumerable. Every type of datatype that can hold more than one value implements IEnumerable (or should) and makes your method hugely flexible.
IEnumerable allows you to iterate through C# IList Nedir a collection. ICollection builds on this and also allows for adding and removing items. IList also allows for accessing and modifying them at a specific index. By exposing the one that you expect your consumer to work with, you are free to C# IList Nerelerde Kullanılıyor change your implementation. List happens to implement all three of those interfaces. If you expose your property birli a List or even an IList when all you want your consumer to have C# IList Nerelerde Kullanılıyor is the ability to iterate through the collection. Then they could come to depend on the fact that they sevimli modify the list.