On Oct 21, 2011, at 2:03 PM, Eric Jacobs wrote: > As a language end-user, I'm not sure that I would (or should) be concerned > about the distinction between a deep continuation and a chain of shallow > continuations. After all, the stack is just a chain of frames, and the > mechanism by which those frames are chained together is not of semantic > importance to the language.
My point was simply that it ain't "coroutines" or "deep continuations" if you are required to say yield at each frame. > That said, coroutinish features like having stacktraces that show multiple > levels of blocking operations, and try/catch blocks that can catch over > several blocking operations would be really nice to have. If those features > can be built at the library level using shallow continuations or generator > trampolines or what have you, I say great. That's the plan. Deep continuations are out for the two reasons (implementor diversity vs. interop, run-to-completion auditability) I gave. /be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
