yosh on Nostr: Wait, so if `for..in` is the “consume” part of the iteration effect, I think ...
Wait, so if `for..in` is the “consume” part of the iteration effect, I think `break` maps to a logical return, and `continue` maps to the next iteration.
I’ve seen people talk about “break with value” before - e.g. the loop exiting with a value. But I don’t think I’ve seen people talk about “continue with value before”.
The latter seems like it would rather neatly map to coroutines, wouldn’t it? E.g. `continue 12u32;` to resume the coroutine with a u32 could work?
I’ve seen people talk about “break with value” before - e.g. the loop exiting with a value. But I don’t think I’ve seen people talk about “continue with value before”.
The latter seems like it would rather neatly map to coroutines, wouldn’t it? E.g. `continue 12u32;` to resume the coroutine with a u32 could work?