4 ms·
Go has a runtime that has to be included, with GC running alongside the app. So no, it is not at all a good fit for Wasm, until the latter’s GC proposal gets fi
by kaba0 5y ago
Go has a runtime that has to be included, with GC running alongside the app. So no, it is not at all a good fit for Wasm, until the latter’s GC proposal gets finalized.
- adrianfcole 5y ago(wazero maintainer) we have a popular allocation example, which shows how GC ends up embedded (really malloc/free) in wasm produced by Rust or TinyGo. You are right that whatever produces wasm, if needs to allocate memory, is doing that by embedding some implementation into the wasm (during compilation). [1] https://github.com/tetratelabs/wazero/tree/main/examples/allocation https://github.com/tetratelabs/wazero/tree/main/examples/all...