Adrian Cole

We could add a special-cased option to CompileConfig which can understand Go's naming convention and make exports as if it was done correctly in the first place. Ex taking an...

I wanted to chime in as things develop. Firstly, I really appreciate the hints @inkeliz gave including the "no compatibility" promise from go. History has told me that blocking on...

@prep sounds good. FYI to test portability of the sys interfaces needed (ex nanotime etc), I started [porting the exec_wasm.js](https://github.com/tetratelabs/wazero/pull/621) yesterday. I'll keep going on this and once done compile...

@cherrymui @aclements I think most of the ecosystem are stumped about the purposed of the "go" "debug" function import when targeting `GOOS=js GOARCH=wasm`. Best I can tell, it accepts the...

FYI the host side implemented here needn't do any goroutine safely, and really should highly discourage anyone from trying to do that. It may seem odd because Go makes some...

https://github.com/tetratelabs/wazero/pull/621 should solve this

Agreed. There's a lot to think about on this one because it also affects anything with ValueType support, ex Globals. Generics are a neat idea, and this also applies to...

For evaluation of whatever next API, clarifying the known consumers of our APIs: * low level SDK or power user: uint64s with codec functions are tolerable, but another API better...

this is an interesting view. bear in mind, we deferred doing things like this because 128 is two uint64s. that said in the approach you are suggesting above, the caller...

food for thought: while we're discussing is the caller side, we've already implemented the callee side (host functions). This code will change for v128 for example (consuming 2 64bit blocks...