Re: Continuations

On Mon, 15 Jul 2024 14:12:32 -0400, EricP wrote:

The effect is that code bounces from action routine to action routine
carrying its execute context with it, waiting for something external,
evaluating the result and deciding what action to do next.

The thing that coroutines bring to the table is that you don’t have to
break up the code that executes in this common context into separate
pieces that are each invoked via a callback and end in a reschedule call.
Intead, you just write it as a single block, with explicit “await” calls
at the various points along the way where rescheduling happens.

The net result is the logic is much easier to follow, and there is often
less of it.