If your class is a custom collection class then yes, it should implement IEnumerable. In this case a public property for the inner list would be redundant. Imagine a simple class:
Queue ve Stack: Queue ve Stack kadar done konstrüksiyonları da IEnumerator kullanılarak elemanlarının sırasıyla yahut aykırı sırasıyla aksiyonlenmesi katkısızlanabilir.
GetEnumerator metodu, bir sınıfa iterasyon mimarilarını kazandıracak özellikleri çitndıran IEnumerator nesnesi dönen bir metotdur.
Ya. Şu esas kadar hiç IEnumerable ve IEnumerator interfacelerini kullanmadım diyebiliriz. Hadi gelin şimdi bu interfaceleri hiçbir uslu ele alalım ve bu tam mafevkdaki satırlarda bahsettiğimiz GetEnumerator metodunuda tam teferruatlı masaya yatıralım.
C# IEnumerable, IEnumerator Mabeyin yüzleri ve Kullanımı hatsında bahsettiğimiz kadar bir klasımızın iterator özelliği kazanabilmesi dâhilin IEnumerable veya IEnumerable interfacelerini implemente etmesi gerekmektedir.
Basically it saf a method to get the next item in the collection. It doesn't need the whole collection to be in memory and doesn't know how many items are in it, foreach just keeps getting the next item until it runs out.
Whenever I'm "stacking" LINQ expressions, I use IEnumerable, because by only specifying the behavior I give LINQ a chance to defer evaluation and possibly optimize the program. Remember how LINQ doesn't generate the SQL to query the database until you enumerate it? Consider this:
IEnumerable and IEnumerator are both interfaces. IEnumerable saf just one method called GetEnumerator. This method returns (as all methods return something including void) another type which is an interface and that interface is IEnumerator. When you implement enumerator logic in any of your collection class, you implement IEnumerable (either generic or non generic).
Usually you don't use IEunumerable directly. It is the base class for a number of other collections that you are more likely to use. IEnumerable, for example, provides the ability to loop through a collection with foreach.
I do have one question though. In the first example you loop over the array using foreach but then you cannot do it in the second example. Is this because the array is in a C# IEnumerable Temel Özellikleri class or because it contains objects?
" This is false, because the where clause is getting called on an IEnumerable and that only knows how to loop through objects which are already coming from the database. If you made C# IEnumerable Nedir the return of AllSpotted() and the parameters of Feline() and Canine() into IQueryable, then the filter would happen in SQL and this answer would make sense.
Generally, don't worry about what's actually in the IEnumerables, kakım it will be completely different from your actual code. Only worry about the actual C# IEnumerable Kullanımı output when you iterate over it :)
Then you'll never have more than one line of the file in memory at a time, and if you finish the loop earlier C# IEnumerable Kullanımı (perhaps it was a search and you found what you needed) you might hamiş need to read the whole file. Or if you're reading the results from a large SQL query you kişi limit your memory use to a single record.
Below mentioned small test might help you understand one aspect of difference between IQueryable and IEnumerable. I've reproduced this answer from this post where I was C# IEnumerable Temel Özellikleri trying to add corrections to someone else's post