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:

If you niyet to build a public API, it's better to use IEnumerable than List, because you better use the most minimalistic interface/class. List lets you access objects by index if that's required.

Şimdiye derece .Kemiksiz ile aplikasyon vüruttirenler IENumarable ve IENumerator interface mimarilarını birmebzul yerde gördük veya bilincinde olmadan çok kullandık amma ne medarımaişete yarıyor niçin bu çatlak yüzlere ihtiyaç duyulur nerelerde kullanabilirim üzere sorulara bu makalemizde yan vereceğiz.

What rights does an employee retain, if any, who does derece consent to being monitored on a work IT system?

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 bey one example.

The syntax (which you rarely see because there are prettier ways to do it) for moving through a collection that implements IEnumerable is:

Ryan LundyRyan Lundy 208k4141 gold badges183183 silver badges214214 bronze badges 3 4 Then why do we need this IEnumerable abstraction, if the only thing it does is just provide an access to Enumerator? Why don't just use Enumerator instead

Is "parse out" actually a phrasal verb, and in what context do you C# IEnumerable Temel Özellikleri use "parse" more hot questions

) without affecting original veri." is confusing. Do you mean that the new list returned C# IEnumerable Nerelerde Kullanılıyor can been added to, and elements yaşama be removed but no updates? I thought that because it returned ienumerable C# IEnumerable Kullanımı you yaşama modify the elements in the list, i.e. change a property like you said but you emanet't add and remove items in the list. Is that correct?

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' veri if it's able to do so or throw an exception if it sevimli'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.

Any idea why the Enumerable is "split" into "inner" and "outer"? This happens when I inspect the element in debug/break mode via mouse. Is this perhaps Visual Studio's contribution? Enumerating on the peşin and indicating input C# IEnumerable Nedir and output of the Enum?

But if your class cannot act like a collection then provide a public IEnumerable property for its elements:

C# dilinde, IEnumerator özellikle adidaki kabil koleksiyonlar üzerinde bilgi okuma ve ustalıklemlerinde yeğleme edilir:

The most important thing to realize is that, using Linq, the query does not get evaluated immediately. It is only run as part C# IEnumerable Kullanımı of iterating through the resulting IEnumerable in a foreach - that's what all the weird delegates are doing.