Ben L. Titzer

I agree with @dschuff. Instead of a file format, we should standard debugging protocol API (similar to JVMTI or JDWP) which would give programmatic access to the WASM-machine-level state and...

I really like this proposal and I am glad it is happening now! 👍 One additional use case I can think of is to implement the equivalent of `.ro` sections...

I generally agree with @fitzgen here. I think we should put first-class memories into their own proposal; we'll have to design a way to allow all memory operations that currently...

> To me, the biggest issue with features indicated in the above discussion would be what happens if the system is unable to commit a a page (assuming they were...

A wasm engine inside of Minecraft? I say why not!

I generally support developing a standard way to reference instructions in code sections so that they become visible in tools, and second @tlively's point that we should use byte offsets...

It's worth noting that in the given example, engines are already optimizing sequences of `load` / `compare` / `branch` into single instructions in their optimizing tiers, by virtue of going...

I don't think checked exceptions works for languages without checked exceptions. E.g. in a language without checked exceptions, but nevertheless different exception types, compiling to wasm where all thrown exceptions...

Languages other than Java may not have an available supertype of all exceptions like `java.lang.Throwable`, so they would have to introduce one (though to be fair, in the current proposal...

I think clamping to page sizes would cripple this feature and result in a proliferation of user code that tries to divide original requests into a page-multiple-sized chunk followed by...