wasm2go

I've added it, to one of my repos, and yes, it's slower than using emulation. Particularly for my use case, Go cross compilation, QEMU and binfmt work really well together. Still, for some things, it's nice to test on actual hardware. Here's a workflow so you can see both approaches working: https://github.com/ncruces/wasm2go/blob/main/.github/workflo...

I built my latest side project (a Wasm to Go "transpiler") precisely as a way to push the limits of what I could do with an LLM/agent. It sped me up (and genuinely helped with some ideas) but not 10x. The bits I didn't design myself I definitely needed to inspect and improve before the ever eager busy beaver drove them to the ground. That said, I'm definitely impressed by how a frontier model can "reason" about Go code that's building an AST to generate other Go code, and clearly separate what's available at generation time vs. at runtime. There's some sophistication there, and I found myself telling them often "this is the kind of code I want to generate, build the AST." I also appreciated how faster models are good enough at slightly fuzzy find and replace. Like I need to do this refactor, I did two samples of it here, can you do these

If you consider just Wasm 1.0 and 2.0, the amount of “runtime” is relatively sparse. A tool like wasm2c (or my wasm2go) shows this: there is no huge runtime to carry, just a fairly direct translation of Wasm byte code to C (or Go). wasm2c: https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... wasm2go: https://github.com/ncruces/wasm2go

I guess someone read the “announcement” that I'm now confident enough this will work that I'll be switching my mildly popular SQLite bindings to use it: https://github.com/ncruces/go-sqlite3/discussions/361 If you're interested in generated sample code, see: https://github.com/ncruces/wasm2go/tree/main/testdata If you're interested in using wasm2go, but feel that something is missing, I'm listening. Caveat: I don't plan to implement any host modules myself (e.g. WASI), but you're welcome to build your own. I'm open to supporting additional Wasm proposals, if feasible, and if they get some use. Examples: I don't think tail-calls are feasible; I assume exception handling could be useful for C++; and I'm definitely interested in dynamic linking support.