Wotcher TAG!

I'm requesting a TAG review of the WebAssembly Garbage Collection (Wasm GC) proposal.

The GC proposal adds efficient support for high-level managed languages to WebAssembly, via struct and array types that enable language compilers targeting Wasm to integrate with a garbage collector in the host VM.

• Explainer: GC proposal overview
• Specification URL: MVP spec, MVP JS API
• Tests: https://github.com/WebAssembly/gc/tree/main/test/core/gc
• Security and Privacy self-review
• Primary contacts:
  • Adam Klein (@ajklein), Chromium feature owner (Google)
  • Andreas Rossberg (@rossberg), proposal champion (independent)
  • Thomas Lively (@tlively), GC subgroup chair (Google)
• Organization(s)/project(s) driving the specification: WebAssembly Community Group members, including Google Chrome
• Key pieces of existing multi-stakeholder review or discussion of this specification: Meeting notes
• External status/issue trackers for this specification: Spec issue tracker

Further details:

• I have reviewed the TAG's Web Platform Design Principles
• The group where the work on this specification is currently being done: WebAssembly Community Group, CG Subgroup
• The group where standardization of this work is intended to be done (if current group is a community group or other incubation venue): WebAssembly Working Group
• Major unresolved issues with or opposition to this specification: None; there is a high level of consensus for the current proposal, as evidenced by its state at Phase 3 of the Wasm CG process

You should also know that:

• VM implementations are under way in V8 (Chromium), JSC (WebKit), and SpiderMonkey (Firefox)
• Language toolchain implementations targeting Wasm GC are underway, including Java, Dart, Kotlin, and OCaml
• In web browsers, integration with the host VM means that Wasm and JS objects can participate in object graphs without creating uncollectible cycles
• Because the GC proposal has been under development for several years, some material in the repo may be out of date (e.g., the "MVP-JS.md" document is no longer part of the proposal)

We'd prefer the TAG provide feedback as:

💬 leave review feedback as a comment in this issue and @-notify ajklein