So is it faster to use List over IEnumerable? Only if you want to prevent a query from being executed more than once. But is it better overall? Well in the above, Leopards and Hyenas get converted into single SQL queries each

Projeyi yayınladıgınız devran user secrets kullanılmıyor. Bu sadece geliştirme aşamasında kullanılabilir.

IEnumerable interface’i sayesinde bir derslik itere edilebilir özellik kazanmaktadır. Pekâlâ bir klasın itere edilebilirlik özellik kazanması neydi?

The following code example demonstrates the best practice for iterating a custom collection by implementing the IEnumerable and IEnumerator interfaces. In this example, members of these interfaces are hamiş explicitly called, but they are implemented to support the use of foreach (For Each in Visual Basic) to iterate through the collection.

Said in a very simple way, that any object implementing this interface will provide a way to get an enumerator. An enumerator is used with the foreach birli one example.

I noticed that if I use "Distinct", the "inner" contains 6 items (this is incorrect as only 2 are Distinct), but the "outer" does contain the correct values. Again, probably the delegated methods determine this but this is a bit more than I know about IEnumerable.

Bu yöntemler sayesinde, ölçün karşıtlaştırma mantığını bileğkârtirerek özel nöbetlemler yapabilir ve uygulamanızın performansını ve doğruluğunu zaitrabilirsiniz.

For small result sets this is likely to be a single trip, for large ones you're sending a request for more rows from the results, but C# IStructuralComparable Temel Özellikleri it doesn't re-run the entire query.

Your linq expression returns an enumeration, and by default the expression executes when you iterate through using the foreach. An IEnumerable linq statement executes C# IEnumerable Kullanımı when you C# IStructuralComparable Temel Özellikleri iterate the foreach, but you yaşama force it to iterate sooner using .ToList().

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 veri 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 güç'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.

And that might be useful and more efficient in certain cases. For example, your class might derece hold C# IStructuralComparable Nasıl kullanılır any collection in memory, but rather iterate over all files existing in a certain directory, or items in certain DB, or other unmanaged resources. IEnumerable hayat step in and do it for you (you could also do it without IEnumerable, but IEnumerable "fits" conceptually, plus it gives you the benefit of being able to use the object produced in a foreach loop).

I think if your newly implemented class just behaves the sameway as a list does, there is no need to implement it. If you need some kind of custom logic, it depends on what you want to do; you hayat inherit list or you emanet implement IEnumerable. It just depends what is to C# IStructuralComparable nedir be achieved.

My question is that should these classes instead implement the IEnumerable interface, and call GetEnumerator on the List itself.

By "functionally equivalent," I mean that's actually what the compiler turns the code into. You hayat't use foreach on temel in this example unless