Interesting. I started working on this same idea a couple of years ago as a way to bypass CGo. Eventually I moved on to something else. Glad someone else is working on this. How does the generated Go performance compare to the original WASM performance?
That's going to depend on what you mean for "original Wasm performance".
What were you using to run Wasm instead of this?
I can compare with wazero, which I was previously using, and say performance stayed mostly in the same ballpark. Things that crossed the Go-to-Wasm boundary very often became much faster, things that stayed mostly in Wasm became slightly slower, as the wazero compiler is pretty good.
wasm2go also does not support SIMD, so if your Wasm module uses/benefits from SIMD, you'll notice.
