4 ms·
There is a WebAssembly proposal called "Threads". https://github.com/webassembly/threads https://github.com/webassembly/threads "This proposal adds a new shar
by richdougherty 4y ago
There is a WebAssembly proposal called "Threads".
https://github.com/webassembly/threads https://github.com/webassembly/threads
"This proposal adds a new shared linear memory type and some new operations for atomic memory access. The responsibility of creating and joining threads is deferred to the embedder."
As for the current status, it is listed on the proposals page: https://github.com/WebAssembly/proposals https://github.com/WebAssembly/proposals
The "Threads" proposal is in "Phase 3 - Implementation Phase" which means it's starting to be implemented, but it hasn't reached "Phase 4 - Standardize the Feature" where 2+ browsers implement it. The final stage would be "Phase 5 - The Feature is Standardized. See https://github.com/WebAssembly/meetings/blob/main/process/phases.md https://github.com/WebAssembly/meetings/blob/main/process/ph...
- Animats 4y agoUseful info is here: https://github.com/WebAssembly/threads/blob/main/proposals/threads/Overview.md https://github.com/WebAssembly/threads/blob/main/proposals/t... Atomics are well covered. The "wait" and "notify" primitives map efficiently to mutexes. "Blocking on the main thread is not allowed, so we can't call lockMutex." The main thread is special in WebAssembly land. Is it still the only one that can do graphics?