Implement wasm-threads (atomics) proposal
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 512
- Forks
- 51
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 21
Description
The WebAssembly Threads proposal introduces a set of ~67 bytecodes that perform atomic operations on memory. Though still at Phase 3, this proposal has been implemented in Web browsers and is effectively finished. Wizard should implement these atomic operations, which primarily involves work in the execution tiers. Currently, Wizard already has placeholders for the opcodes in his large Opcode enum--thus work is already scoped.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the large Opcode enum to review the existing atomic-opcode placeholders, then trace how opcode execution is handled across the execution tiers. Done means implementing the WebAssembly Threads atomic operations so they execute correctly across those tiers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100