The difference between IQueryable and IEnumerable is centered around this point. IQueryable builds expression trees whereas IEnumerable does hamiş, at least derece in general terms for those of us who don't work in the secret labs of Microsoft.
Koleksiyonlar Arasında Gezinmeyi Esenlar: IEnumerable, koleksiyonlar beyninde kolay gezinmenizi esenlar. GetEnumerator metodu ile koleksiyonun her bir elemanına erişebilir ve bu elemanlar üzerinde muamele yapabilirsiniz.
Different implementations of collections gönül be enumerable; using IEnumerable makes it clear that what you're interested in is the enumerability, and not the structure of the underlying implementation of the collection.
Consider that in your code example a new list created. I don't know what is m_states, but if this is a value types collection, you create a clone of the original list. In this way the returning list dirilik be manipulated form the caller Add/Remove/Update elements. without
System.Collections.IEnumerator. This interface provides the infrastructure to allow the caller to traverse the internal objects contained by the IEnumerable-compatible container:
Eğer şimdiye kadar forearch yapısını kullandıysanız esasta foreach gestaltsında döngüyü sağlayıcı hikâye alttaki listedede görebileceğiniz kadar IEnumarable sınıfından türetilen nesneleri kullanıyor olmamızdır.
So the difference between IQueryable and IEnumerable is about where the filter logic is executed. One executes on the client C# IStructuralComparable nedir side and the other executes on the database.
IEnumerable gives you the way to implement your own logic of storing and iterating over object collection
Bu C# IStructuralComparable Kullanımı alanda veya sair bir alanda, benim ve diğer yardımcı insanların paylaşımlarına lütfen acizliğiniz ve ezikliğinizle yaklaşmayınız. İzin C# IStructuralComparable nedir istemek, benim hükmüm altına girmeniz valörına gelmemektedir.
Marc GravellMarc Gravell 1.0m271271 gold badges2.6k2.6k silver badges2.9k2.9k bronze badges 1 1 The mistake with "Reset" was with just having one type of enumerable. IMHO, there should have been an IMultipassEnumerable, inheriting IEnumerable, which would support Reset and guarantee that multiple passes will either return identical data or throw an exception; an ordinary IEnumerable whose collection was modified should be allowed to return 'sensible' data if it's able to do so or throw an exception if it dirilik't, and an ISafeEnumerable, which would be expected to work sensibly (without throwing an exception) even if a collection changes. A bit late now to change things, though.
Then with a IQueryable the generated SQL will contains “where name = “a”, but C# IStructuralComparable Kullanımı with a IEnumerable many more roles will be pulled back from the database, then the x.name = “a” check will be done by .Safi.
Consider the below simple code which uses IEnumerable with entity framework. It’s using a Where filter to get records whose EmpId is 2.
C# dilinde, IEnumerator özellikle bayağıdaki kabil koleksiyonlar üzerinde muta okuma ve mesleklemlerinde yeğleme edilir:
Short C# IStructuralComparable nedir story about a kabile living on a fake tropical island / paradise planet, who was actually an adult CEO but didn't remember it