4 ms·
With WasmGC finalized, I hope we see more compilers that target it instead of including their own GC. It's could be a new interpreter, or maybe a version of CP
by spankalee 3y ago
With WasmGC finalized, I hope we see more compilers that target it instead of including their own GC.
It's could be a new interpreter, or maybe a version of CPython that uses WasmGC structs for all Python objects, or a compiler similar to this but that targets WasmGC directly.
- Jasper_ 3y agoWasmGC is not really what you think it is. Think of it as a full-on replacement for the linear memory model, not as a way to add GC to it. It's exceptionally difficult to port a language runtime over to WasmGC -- it doesn't even offer finalizers, so __del__ can't implemented correctly (even ignoring the issues with existing __del__ semantics in Python leading to compatibility issues). It doesn't support interior pointers, so you can't have a pointer into the middle of an array. There's no easy way to port Python to WasmGC.
- kevingadd 3y agoCurrent WasmGC is missing a lot of critical features for production grade GC, like finalization and interior pointers. It's really promising though, so I think once the gaps get filled in you'll see a bunch of runtimes start moving over - maybe .NET, etc.