Francis McCabe
Francis McCabe
I am still trying to grok why the "non-shared-suspendable" -> "shared-suspendable" boundary is different to "non-shared"->"shared".
In fact, even with typed continuations (wasmfx), you will still need to prohibit interleaving JS frames with wasm frames in an active computation. In particular, when you suspend to a...
I don't think that wasmfx and bos are any different here.
Since I am not personally familiar with AS it is hard to be sure how to interpret this. However, you may be under a mis-apprehension about the intended audience for...
The stack switching effort aims primarily at a standard-compliant implementation of features like these. In addition, the use cases for stack switching go beyond longjmp/setjmp; some of which are quite...
Are you aware that there are actually two proposals for stack switching?
In fact, my preferred approach is documented [here](https://gist.github.com/fgmccabe/afe8bdfdf2ffdc94d69252683f376d15). Even simpler than the fibers approach.
I would prefer to keep this open for now. There is a connection to the discussion around the barrier instruction
The issue with that approach is recovering the identity of the task from a suspended computation; in particular a continuation has no other information accessible from outside than the continuation...
I understand that. But you have to pick the identity up when you suspend. At best that means storing it in a global when you resume the continuation. But there...