On Wednesday, 8 November 2023 at 13:52:34 UTC, Richard (Rikki)
Andrew Cattermole wrote:
On 09/11/2023 2:42 AM, Hipreme wrote:
If the runtime is not revived, there is no point in having a
GC at all, and it is impossible to use the GC without the
runtime, but runtime without the GC, it is possible :)
That's not true.
You wouldn't need anything in druntime to make the wasm GC
work. Everything would be done in the glue layer of the
compiler and would be specific to that target.
The druntime bits for GC or TypeInfo wouldn't be used.
Yes, the wasmgc's main selling point is the sharing of GC and
TypeInfo between Javascript and WASM.
Sharing of data between the JS/WASM are problematic. JS has no
destructor, so it practically impossible to do manual
memory/resource management in JS side; One has to do a lot of
works to pass data around. c/c++/rust, non-gc system languages,
are not a good fit for JS/WASM, but D if ported to wasmgc would
be a great fit.
I think D is in a happy position here.
