Derek Schuff

There is a very real possibility that we will never be able to remove phase 3 exceptions from the web, at least in the near future. Even if we went...

We discussed exposing a special exception tag for JavaScript and allowing importing it (the payload would be an externref that represents the thrown object): https://github.com/WebAssembly/exception-handling/pull/269 I think something like that...

Now the #301 has landed I did want to briefly bring back up the question of passing exnrefs into JS via function return, global getters, etc. @rossberg mentioned [there](https://github.com/WebAssembly/exception-handling/pull/301#issuecomment-2036355033) and...

I think the issues here have been resolved and the JS API spec now reflects what we discussed here. Let's open specific new issues if there's anything new.

https://github.com/WebAssembly/multi-memory/pull/27 raised the limit on the number of memories in the JS API from 1 to 100. I'm not sure anything more needs to be done to the JS API...

wasm-e2e hasn't really been updated in a while. If you want to test integration between v8, sexpr-wasm, binaryen, emscripten, and LLVM, it might be easier to try the continuous build...

Regarding 2), I'd say that in general we want to get some diversity of implementations if possible. For example it would be better to get one blockchain embedding and one...

Regarding 3), I think mirroring the CG/WG split from the main phase process (where the "CG" there is the subgroup here, and the "WG" is the CG), is a good...

On Wed, May 15, 2019, 3:47 PM Luke Imhoff wrote: > replace “Web VMs” with “implementations” and leave it up to the committee > > This is fine to me....

I'll be there. wrt discussion topics, maybe we should try to focus on where the debugging discussions impact the larger group. For example wrt your first bullet point there are...