What would the GC scan? What do pointers look like? At the assembly layer, you have the flexibility to not have a C runtime (and therefore no C stack), and you might be doing fun things like having tagged pointers that the GC would have to know about.<p>In short, the WASM layer is IMO the wrong layer for GC. I think the closest-layered applicable solution is caching &amp; pinning guarantees for common libraries, which may already be addressed by the same solutions for common JS libraries (use a common CDN &amp; let the browser caching keep it pinned).