If I use yield instead of manually creating an IEnumerator, is it possible to implement IEnumerator.Reset?
The yield keyword tells the compiler that the method in which it appears is an iterator block. yield return <expression>; yield break; The yield return statement returns one element at a time. The return type of yield keyword is either IEnumerable or IEnumerator .
The advantage of using yield is that if the function consuming your data simply needs the first item of the collection, the rest of the items won't be created so it's more efficient. The yield operator allows the creation of items as it is demanded. That's a good reason to use it.
You use a yield return statement to return each element one at a time. The sequence returned from an iterator method can be consumed by using a foreach statement or LINQ query. Each iteration of the foreach loop calls the iterator method.
It specifies that an iterator has come to an end. You can think of yield break as a return statement which does not return a value. For example, if you define a function as an iterator, the body of the function may look like this: for (int i = 0; i < 5; i++) { yield return i; } Console.
No, it is not possible. When the C# compiler processes an iterator (a method that contains a yield
statement), the compiler generates a class that implements IEnumerable and IEnumerator. The generated class' implementation of Reset just throws a NotSupportedException. There is no way to influence this in current versions of C#.
Instead, your calling code will need to request a new enumerator, i.e. begin a new foreach loop. Or you will need to forgo the language support (the yield
statement) and write your own class which implements IEnumerator.
There is no built-in support, but you can define your own implementation of IEnumerator
that delegates all method calls to the enumerator generated by C# and only lets you define your own behavior for the Reset
method.
The simplest version of the class would look like this:
class ResetableEnumerator<T> : IEnumerator<T>
{
public IEnumerator<T> Enumerator { get; set; }
public Func<IEnumerator<T>> ResetFunc { get; set; }
public T Current { get { return Enumerator.Current; } }
public void Dispose() { Enumerator.Dispose(); }
object IEnumerator.Current { get { return Current; } }
public bool MoveNext() { return Enumerator.MoveNext(); }
public void Reset() { Enumerator = ResetFunc(); }
}
In this case, the ResetFunc
that you specify returns a new IEnumerator<T>
, so your provided implementation of ResetFunc
can do some cleanup or whatever you need to do when resetting and then return a new enumerator.
IEnumerator<int> Foo() { /* using yield return */ }
IEnumerator<int> PublicFoo() {
return new ResetableEnumerator<int> {
Enumerator = Foo(),
ResetFunc = () => {
Cleanup();
return Foo(); } };
}
You'll need to store all the originally local variables of the Foo
method as fields of the class, so that you can access them in Cleanup
(Note that the rest of the Foo
body will never be executed after calling Reset
), but that's still easier than writing a handwritten iterator!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With