dcodeIO

The crucial aspect to me is that there should not be glue code necessary for essential functionality on the Web respectively common functionality on/off the Web, as I believe that...

Also, with this issue being open for nearly a month now, and sadly hardly any of the IT/WASI folks chiming in to improve the situation, I decided to attempt myself...

Duplicate imports are quite useful to call imports from dynamic languages like JS, where the same function can have various signatures, and I'd expect it to be used rather more...

The core problem I see is that a user has to know all the arities and argument types upfront to manually mangle the imports object, while currently a compiler can...

> In all scenarios that I've seen, the JS code that instantiates a wasm module is generated by the same toolchain that generates the wasm module (b/c instantiation in general...

Fwiw, by my understanding titzer's suggestions to make Wasm viable for more use cases rather than less is much more in-line with my expectation than the alternative. I would even...

I appreciate the ambitious vision as presented, yet I am still very worried about the [choice of picking UTF-8 as the sole canonical representation for strings](https://github.com/WebAssembly/interface-types/pull/132/files) in an IT MVP,...

Sounds reasonable, thanks. One more question perhaps: Do you think it would make sense to delay the decision to split out adapter functions from an IT MVP, since splitting to...

Related: https://github.com/WebAssembly/design/issues/1210 which proposes an event handler.

Fwiw, we have been anticipating the addition of `bswap` over at AssemblyScript and are currently polyfilling them. We'd also be interested if these were made available as instructions.