WebAssembly / WebAssembly/threads
Coordinate WebAssembly memory model changes w/ ECMAScript (via TC39)
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
This is a tracking issue to coordinate the changes to the memory model we discussed in previous CG meetings w/ ECMAScript.
- Require 1- and 2-byte atomics to always be lock-free
- Remove
is_lock_free-- should this be removed from ES as well?
Are there others?
Contributor guide
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 issue #71 and the prior CG meeting discussions it references, then review how the proposed WebAssembly memory-model changes align with ECMAScript through TC39. Done means reaching agreement on the lock-free atomic requirements, the fate of is_lock_free, and any additional coordinated changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100