Skip to content

Implement a GC feature that uses the JS heap from the Wasm runtime without WasmGC proposals#3

Open
itsu-dev wants to merge 4 commits into
masterfrom
feature/grower-gc
Open

Implement a GC feature that uses the JS heap from the Wasm runtime without WasmGC proposals#3
itsu-dev wants to merge 4 commits into
masterfrom
feature/grower-gc

Conversation

@itsu-dev
Copy link
Copy Markdown
Contributor

@itsu-dev itsu-dev commented Apr 20, 2026

About

In PPL2026, we proposed GC-like memory management system for managed language runtimes mostly running on WebAssembly runtimes. The main metholodgy of that idea is that all of runtime objects are represented as Uint32Array and placed on the JS heap, then referenced opaquely from programs runnning on the WebAssembly runtime via the table. Most of features are implemented in Tsukuba-Programming-Lab/BJVM, but because their implementation should be based on Grower for some implementation reasons, features related to linear-memory are implemented as Grower project. We are now planning to implement all the features on Grower with some abstractions.

@itsu-dev itsu-dev changed the title Implement a GC feature that uses the JS heap from the Wasm runtime z Implement a GC feature that uses the JS heap from the Wasm runtime without WasmGC proposals Apr 20, 2026
@itsu-dev itsu-dev self-assigned this Apr 20, 2026
@itsu-dev itsu-dev added the enhancement New feature or request label Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant