Interesting. Apparently this uses the Windows terminology "fiber" =
coroutine. But there's also threading, and it's unclear what
relationship the library establishes between threads and coroutines?
I would guess the dependency on Boost is for the fiber execution state.
Cheers, & thanks,
- Alf
PS. Oh, by the way, the output driven solution (the thread you replied
in here) is not a multitasking solution. It's just an unnatural solution
based on choosing an impractical top level goal for a procedural
stepwise refinement. But interesting as such, keeping in mind Betrand
Meyer's "real systems have no top".