Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @tonyfreeman,
Sorry to abuse a PR this way but it's the only way I could find to get in touch. I was wondering about the suitability of this code for something I'm working on. It's a little language interpreter written in "trampolined continuation-passing style.” The key point is that the interpreter's user gets control back after each unit of work. CPS can be awkward, and it would be much cleaner to intersperse
yield
s in a regular eager recursive interpreter implementation, run as a fiber, and just keep poking the fiber to move to the next step. But the examples I see here don't make it clear whether I can build such a structure.Channel
looks kind of close; I wonder if you can offer any insight? Thanks!