Conversation
Chrome, wasmtime and wasmer were a little outdated / inaccurate.
| "saturatedFloatToInt": true, | ||
| "signExtensions": true, | ||
| "simd": "2.0", | ||
| "threads": null, |
There was a problem hiding this comment.
I don't know if it's accurate that they don't have threads support, but it's at least more accurate than saying that threads support is not applicable.
There was a problem hiding this comment.
Seems like this was semi intentional considering there was no way to spawn threads (#313 (comment)), but this isn't the case anymore. There's a Rust target wasm32-wasi-preview1-threads that supports spawning threads and wasmtime supports it.
There was a problem hiding this comment.
Yeah, if there's now a way to spawn and use threads in these runtimes, I think it makes sense to mark this as supported. The exact mechanism for that (web workers, a WASI or even a nonstandard interface) is outside the scope of the core spec, and probably outside the scope of this page as it's currently designed. It might be helpful to find a way to link to some information (maybe just as an annotation alongside our long list of flags or something) but I think what you have proposed here is still an improvement over the current version. (and I think I'd accept a PR marking threads as supported behind a flag or whatever).
Runtimes that don't target JavaScript don't need to support JSPI.
| "saturatedFloatToInt": true, | ||
| "signExtensions": true, | ||
| "simd": "2.0", | ||
| "threads": null, |
There was a problem hiding this comment.
Yeah, if there's now a way to spawn and use threads in these runtimes, I think it makes sense to mark this as supported. The exact mechanism for that (web workers, a WASI or even a nonstandard interface) is outside the scope of the core spec, and probably outside the scope of this page as it's currently designed. It might be helpful to find a way to link to some information (maybe just as an annotation alongside our long list of flags or something) but I think what you have proposed here is still an improvement over the current version. (and I think I'd accept a PR marking threads as supported behind a flag or whatever).
|
I'll go ahead and merge this, we can iterate more on how to handle threads if there is interest. |
2 participants
Chrome, wasmtime and wasmer were a little outdated / inaccurate.