Nuno Cruces

Thanks for the heads up. I think this is mostly ready, I just need to update CI to download the v0.32 binaries, and run tests.

Linux binaries still missing from [here](https://github.com/tinygo-org/tinygo/releases/tag/v0.32.0), will try again.

@deadprogram it seems TinyGo v0.32 lost the ability to build `--target=wasi` binaries with Go 1.20?

This seems fine here, but if you want to open up a discussion with _users_ of wazero, we have a couple of channels in Gophers Slack: [wazero](https://gophers.slack.com/archives/C040AKTNTE0) and [wazero-dev](https://gophers.slack.com/archives/C04CG4A2NKX).

I'd say that, if you want something representative of user relevant Go code that we have, I'd look at a compilation benchmark: take a complex pice of Wasm (could be...

Thanks @dr2chase for approaching us (and staying with us), and @davidmdm for asking the right question! If you're looking for typical usages of wazero, I guess the interpreter is less...

I was able to reproduce it with `amd64`: ``` $ go test -bench='BenchmarkLibsodium/box_seal' -count=100 -benchtime=10x -v goos: linux goarch: amd64 pkg: github.com/tetratelabs/wazero/internal/integration_test/libsodium cpu: AMD EPYC 7B13 BenchmarkLibsodium BenchmarkLibsodium/box_seal require.go:331: expected...

It also seems to happen with the old, 1.6.0, compliler: ``` $ go test -bench='BenchmarkLibsodium/box_seal' -count=100 -benchtime=10x -v goos: linux goarch: amd64 pkg: github.com/tetratelabs/wazero/internal/integration_test/libsodium cpu: AMD EPYC 7B13 BenchmarkLibsodium BenchmarkLibsodium/box_seal...

Well, it imports (and calls) `random_get`, so there's plenty of room for non-determinism in there. ``` $ wasm-dis box_seal.wasm | grep '(import' (import "wasi_snapshot_preview1" "clock_time_get" (func $fimport$0 (param i32 i64...

More is wrapped now, everything except table constraints.