Merge upstream spec/main into threads
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- wasm
- Domain
- compilers
Research direction
Compare this repository with the latest upstream spec repository, using issue #207 as the prior merge reference and checking related issues #240 and #222. Determine the expected merge scope and verify that the resulting threads repository is current enough to fork for the relaxed atomics proposal.
Written by the indexing model from the issue text.
Description
The upstream spec repo hasn't been merged in quite some time (#207 in 2023 may have been the last time AFAICT). We'd like to fork from this repo for the relaxed atomics proposal (which is to be split out from the shared-everything-threads proposal), but to do so we'd like to have this repo be up-to-date first.
Can we merge the latest upstream spec repo into this repo? Also related is #240 and #222.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
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.
More from WebAssembly/threads
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
WebAssembly/threads#254 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
WebAssembly/threads#253 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
WebAssembly/threads#240 ·
-
Branch renaming Open
Difficulty 1/5 Under an hour Newbie friendliness 20/100
WebAssembly/threads#237 ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
WebAssembly/threads#234 · 3 comments ·
All issues in WebAssembly/threads
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo#8923 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
internal.h中,漏掉了1个定义。 Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100