Adrian Cole

@aykevl maybe close out this then? open PRs are distracting especially in reflect which is spread across so many things. I think that people knowing what won't happen is at...

@hunjixin ps some of the smart contract stuff bled into discussions on wazero and one thing in general was decent fakes. With some trickery the host can actually write wasm...

another motivation to do something like this is even if a host stubs similarly, there's a very real cost to function calls from wasm->host and back. This can cause inconsistency...

So, `srcObject.buffer` is still nill when the coercion happens. I looked a little closer. if you cast inside `main` it works. There may be something lazy that needs to become...

verified this works now. thanks @aykevl!

wazero also maintains this and having written almost all of it, I'm happy to paste it somewhere else also https://wazero.io/languages/tinygo

@brunoluiz ack. the wazero page won't get into details of browser use much as it is vast, and wazero embeds in go apps which aren't likely to include a javascript...

last thing on wazero's page: https://wazero.io/languages/tinygo/#system-calls only applies to the `wasi` target. It isn't used in the `wasm` target, so it should be irrelevant for js. The system call approach...

@rvolosatovs interesting (esp that the snapshot01 version was updated after the fact!). I was curious the motivation of this? Is this a proof of concept or are folks making raw...

@james-lawrence is there anything else to do on this one? ack that [`//export` isn't intuitive to mark something as an import](https://github.com/tinygo-org/tinygo/pull/455#issuecomment-531603663), but for today `//export` is how it is done.