WebAssembly / WebAssembly/threads
Consider supporting verifiably safe concurrency
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
What is the sentiment for supporting a subset of wasm that is verifiably safe with respect to concurrency?
The motivation is to allow modules to interoperate efficiently (lock free, zero-copy), without depending on the correctness of the other party to preserve their safety.
This is an extension of Issue #4 in the GC proposal, which suggests maintaining a verifiably safe subset of wasm.
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
No files or tests are named. Start by reading this issue and the linked GC proposal issue #4, then determine whether the proposed verifiably safe concurrency subset has an agreed scope; done would be a clearly defined proposal or decision on support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100