Heejin Ahn

> There is no need for exception handling to depend on external references, and you can imagine many applications of WebAssembly with exception handling that would not even want external...

`exnref` is an external reference, even if it is not a subtype of `anyref`, in that it is created by the embedder, isn't it?

FYI, this is a summary of the rationale on why we decided not to catch traps, after long discussions: https://github.com/WebAssembly/exception-handling/issues/1#issuecomment-546568318 I think reasons in this summary still stand, and I...

@tlively > Adding new throwing instructions seems clearly simpler than adding hooks or new control flow constructs because it does not introduce anything fundamentally new to the spec and does...

Will this proposal be compatible with the changes I proposed in WebAssembly/exception-handling#123, namely, removal of `exnref`, introduction of `catch_br`, and split of `catch` and `unwind`?

[exception handling](https://github.com/WebAssembly/exception-handling) repo's default branch has been switched to main too.

- Sorry, but I don't really understand what `answer` and `call_stack` do. Can you elaborate, or provide a simple, not-too-long example? - Are you suggesting we redesign the EH proposal...

> > Are you suggesting we redesign the EH proposal from scratch using these instructions? > > Definitely not. This is about stack inspection. Although stack inspection can be used...

In the first phase of EH, `throw` (or `rethrow`) is the instruction that starts the search process. But you sound like we need these separate instructions to start the first...

How does it know the destination stack even before it runs filters and such? What makes this exception special? Also, other than you changed `throw` to `call_stack` and `try`-`catch` to...