Design doc for collecting shared-to-unshared edges
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- wasm
- Domain
- compilers
Research direction
Start by reading the linked V8 GC design document, then compare its full shared-to-unshared cycle-collection plan with the issue's stated initial subset for main-thread-owned unshared objects. The issue does not name files, tests, or a concrete implementation boundary; completion criteria would need to be agreed before work starts.
Written by the indexing model from the issue text.
Description
As promised, here is a link to the design doc the V8 GC team wrote on how we would be able to support collecting cycles involving shared-to-unshared cycles: https://docs.google.com/document/d/1GoIWdfsKuKb0PS3gSF8b1U0RoHs5ALPzXAMx-QPHHNg/edit#heading=h.g227de93gbi
The current plan is to not prototype this right away, and instead initially support collecting cycles with shared-to-unshared edges only when those edges are to unshared objects on the main thread. This subset of the full capability does not require any heroics in our GC because the main thread "owns" the shared heap and is already responsible for doing GC on it along with its own unshared heap.
- Dominant language
- WebAssembly
- Stars
- 97
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/shared-everything-threads
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WebAssembly/shared-everything-threads#119 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/shared-everything-threads#114 · 7 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
WebAssembly/shared-everything-threads#105 · 6 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
WebAssembly/shared-everything-threads#99 · 5 comments ·
All issues in WebAssembly/shared-everything-threads
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
yhirose/cpp-peglib#344 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
build-problem llvm:adt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
llvm/llvm-project#228475 ·
Maintainers usually reply within 1 day