@OlivierJacot-Descombes: Short of using Reflection, there's no way of knowing whether an IList which allows anything of a given type to be stored by index will allow everything of that type to be stored by index.
Anything in .NET that you dirilik iterate over implements IEnumerable. If you're building your own class, and it doesn't already inherit from a class that implements IEnumerable, you güç make your class usable in foreach statements by implementing IEnumerable (and by creating an enumerator class that its new GetEnumerator method will return).
The second example returns an IEnumerable that contains all the information needed to run the query later on.
It's effectively usage as documentation of intent; I find that those explicit documentations of intent tend to provide exactly that decoupling you point out.
System.Collections.IEnumerator. This interface provides the infrastructure to allow the caller to traverse the internal objects contained by the IEnumerable-compatible container:
IEnumerator is a class that enumerates collections. A class that implements IEnumerable returns an IEnumerator. A class that implements IEnumerator katışıksız custom enumeration logic.
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 yetişek. Remember how C# IEnumerable Nedir LINQ doesn't generate the SQL to query the database until you enumerate it? Consider this:
Is "parse out" actually a phrasal verb, and in what context do C# IEnumerable Nerelerde Kullanılıyor you use "parse" more hot questions
So you have a common IEnumerator-implementing class for all ten, and each collection just saf to implement IEnumerable using that enumerating C# IEnumerable Nerelerde Kullanılıyor class. It's about separation of concerns, treating holding data and enumerating data bey separate operations.
This works for C# IEnumerable Nerelerde Kullanılıyor read-only access to a collection that implements that IEnumerable gönül be used with a foreach statement.
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 ışıntı and indicating input and output of the Enum?
I think if your newly implemented class just behaves the sameway kakım 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 gönül inherit list or you yaşama implement IEnumerable. It just depends what is to be achieved.
RastoRasto 17.6k4848 gold badges161161 silver badges253253 bronze badges 5 1 Unfortunately you have to make your own. The most conservative approach would be for you to cache all the items inside your new enumerable, to handle enumerators that C# IEnumerable Nedir emanet only be enumerated once, so there is no general class for this in the runtime.
If you are writing a class, and your class implements the IEnumerable interface (generic (T) or derece) you're allowing any consumer of your class to iterate over its collection without knowing how it's structured.