Do I understand correctly that endive ships with a garbage collector and only uses the host gc when references pass over the API boundary? I don't know much about wasm, but would it be possible to use the host gc for everything? Or is there some inherent property of wasm that makes this impossible / less efficient?
In general, it depends on which features a language runtime needs from a GC, for example, currently the WASM GC proposal is unusable for languages that need internal pointers, thus languages like C# keep shipping their own.
Comments
Do I understand correctly that endive ships with a garbage collector and only uses the host gc when references pass over the API boundary? I don't know much about wasm, but would it be possible to use the host gc for everything? Or is there some inherent property of wasm that makes this impossible / less efficient?
In general, it depends on which features a language runtime needs from a GC, for example, currently the WASM GC proposal is unusable for languages that need internal pointers, thus languages like C# keep shipping their own.