Keith Winstein

I'm a little confused that this only ended up touching the `legacy` tests. Are there new tests for try/br interactions in the current version of this proposal?

Thank you for the presentation today! I hadn't been following this conversation. I implemented the exception-handling support in wasm2c. One of the things that made that easier is the (current)...

Thinking about how we'd implement `exnref` in wasm2c, honestly I think we'd probably just represent is as a fixed-size value type on the stack (probably a struct that contains the...

I got to talk today with @aheejin, @conrad-watt, and @titzer, about the implementability of exnref in wasm2c, and probably in other "offline" VMs that also lack GC. The conclusion seemed...

@tlively Unfortunately I haven't thought of a great way to do reference-counting in wasm2c (and similar offline VMs) without a lot of overhead. Currently our trap handling is just "longjmp...

It might be helpful to have a broader discussion about the deprecation plan for "legacy" (v3) exceptions. My concern would be that the major browsers will never deprecate them (similar...

Sigh. :-/ I think if the browsers are going to keep supporting "legacy-exceptions" forever (and if some producers keep generating them so that their output works on legacy browsers) then...

From one runtime-implementer perspective, it would be helpful if we could - merge this to main so the [testsuite](https://github.com/WebAssembly/testsuite) repo can pick these changes up - update binary.wast to test...

> In fact, it'd be good to have more tests for this proposal in general. Agreed -- I hope we can find a way to merge #270 and #277 now...

Unfortunately I think `extern.convert_exn` would be a problem for wasm2c and other consumers who want to implement exception-handling without a dependency on GC. :-( Per https://github.com/WebAssembly/exception-handling/issues/280#issuecomment-1664945711, my understanding had been...