return value for yield break

[Per6]

IEnumerable<string, int> Hello5() {
    yield return "hello";
    yield break 5;
}

int num = foreach(string s in Hello5()) {}

IAsyncEnumerable should have this as well, returning a Task<T>.

[HaloFour]

That is an interesting idea. How would that final value be communicated through the IEnumerable<T, T2> interface? Presumably it is required that the iterator method return that value via yield break? What are some use cases for this?

[Per6]

yes, yield break should be mandatory if TFinal is used.
my game manager returns IAsyncEnumerable in all functions, so the visual stuff can be handeled in the visual manager but not in the server.
my card effect structure shares that IAsyncEnumerable. right now i can't visually show the cards responsible and the value without an extra class to then have the value as an out parameter, which just makes the structure weird.

[HaloFour]

Seems like it would be simple enough to pass a state object into the iterator method which the iterator could use to pass information back to the caller:

IEnumerable<string, int> Hello5(State state) {
    yield return "hello";
    state.Value = 5;
}

var state = new State();
foreach(string s in Hello5(state)) {}
int num = state.Value;

[Per6]

yes, that would work. it's just a little too unsafe for my liking.

[colejohnson66]

@Per6 How is it unsafe? Because the state could accidentally not be set? An analyzer could help there. Not sure how hard that would be though.

[Per6]

i could:

1. forget to set it
2. accidentally use it in the for loop
3. forget to evaluate the IEnumerable before using the state

I've tried setting up an Analyzer once before but for some still unknown reason it didn't work.