Hi all,
As there was recently not much work on the proposal, I'd like us to define some next steps to move towards finalizing threading support in WebAssembly.
A brief summary of the current state:
- a number of ambiguities around
wasi_thread_spawn host call was clarified
- tests have been added
- tooling support:
- Runtime support:
- Open questions:
I think there are two possible ways we can move forward with the proposal:
- we keep the proposal in its current stage (phase 1) and start work on a proposal for adding threading to WebAssembly (possibly as an extension to the threads proposal.
- we continue the work on this proposal - define phase 2 advancement criteria (I think we're close), resolve all the remaining questions, define the release plan.
My personal opinion is that we should progress with wasi-threads proposal and accept the risk it becomes deprecated in the distant future (if ever) by WebAssembly threads - this approach will enable a number of use cases in short/mid-term that are currently blocked by lack of standardization of threading in the WASI ecosystem. There's already been a lot of discussions on open questions, and it feels like some of them only need a summary and updated documentation before closing, and some of them can be even resolved as follow-ups after this proposal.
I'm looking for others' feedback on that before taking any next steps.
cc @sunfishcode @abrown @sbc100 @AlexEne @yamt
Hi all,
As there was recently not much work on the proposal, I'd like us to define some next steps to move towards finalizing threading support in WebAssembly.
A brief summary of the current state:
wasi_thread_spawnhost call was clarified_start#21wasi_thread_exit(): Iswasi_thread_exitneeded? #7I think there are two possible ways we can move forward with the proposal:
My personal opinion is that we should progress with
wasi-threadsproposal and accept the risk it becomes deprecated in the distant future (if ever) by WebAssembly threads - this approach will enable a number of use cases in short/mid-term that are currently blocked by lack of standardization of threading in the WASI ecosystem. There's already been a lot of discussions on open questions, and it feels like some of them only need a summary and updated documentation before closing, and some of them can be even resolved as follow-ups after this proposal.I'm looking for others' feedback on that before taking any next steps.
cc @sunfishcode @abrown @sbc100 @AlexEne @yamt