Dan Gohman

Overall this looks like a good start. This specifies the browser devtools as the UI that the user will be interacting with. Another idea which has been discussed is that...

That sounds reasonable to me. The number of arguments is already present in the `arg*:vec()` encoding, rather than being inferred from the signature of `$f`, so this makes returns consistent...

The alignment hint was added to the spec with the assumption that compilers would almost always be able to emit it correctly. Alignment hints are always correct in all code...

I'm curious about option 3's goal of maintaining the "purity of the WebAssembly core semantics". It would seem that doing so would require thing we call "the WebAssembly core semantics"...

> They don't take up opcode space With eg. the 0xfc "miscellaneous" prefix, new instructions wouldn't take up significant opcode space either. > They are forward compatible (e.g. you can...

That's a good point. I wonder if it's feasible to modify the wit grammar such that `name:` is always parsed as an identifier and never as a keyword. That would...

`func: func(func: func)` being accepted by the grammer is surprising, but hopefully syntax highlighting will help if this ever comes up in practice.

There are established methods for linear-time verification of irreducible control flow. A notable example is the JVM: with stackmaps, it has linear-time verification. WebAssembly already has block signatures on every...

@comex Another consideration here is how much wasm engines are expected to do. For example, you mention Ion's AliasAnalysis above, however the other side of the story is that alias...

Yes, it's correct. Wasm's floating-point is deterministic, other than NaN bit patterns.