Wasm GC
summary
Wasm GC adds concrete structs and arrays stored in a WebAssembly GC heap, plus runtime type information and a validation/linking scheme engines use to check and connect these types. The talk reports experiments in Chrome, Firefox, and Safari (behind flags) and a JSC implementation, measuring runtime-size tradeoffs—native runtimes can shrink from about 100MB to ~5MB when reusing the browser GC—and shows real-world use (Bergamot translator) while discussing module linking, validation costs, and current tooling behavior under the proposal.
AI-written summary · about
chapters (16)
- 0:00Wasm GC intro
- 4:04What is WebAssembly GC
- 8:06Compiling to Wasm GC
- 11:21Wasm GC type system
- 14:58Why type system for GC
- 20:05Nominal vs structural typing
- 23:16Recursive type checking
- 33:29Final Wasm GC type system
- 34:57GC runtime and JS integration
- 38:08Wasm GC browser support
- 40:12Q&A
- 44:49Q&A
- 47:57Q&A
- 50:25Q&A
- 52:51Q&A
- 56:25Conclusion
related talks
31mWasm GC: What Exactly Is It (and Why I Should Care)
10mMobile app development with WebAssembly GC
30mA Compiler Author’s Guide to WebAssembly GC
22m[Keynote] Wasm GC and the Future of High-Level Language Compilation
57mIs Wasm Becoming Garbage? (Keynote)
17mImplementing and Evaluating a High-Level Language with WasmGC and the Wasm (…)
38mWasm_of_ocaml
22mThe state of WebAssembly