Heejin Ahn

I'll respond there too, but here is the link to a summary of the rationale on why we decided not to catch traps: https://github.com/WebAssembly/exception-handling/issues/1#issuecomment-546568318

Your interpretation is correct. Currently the only reliable way to throw an exception that is uncatchable by wasm is to call into a wasm function that does nothing but trap....

@RossTate Could you elaborate? Catch-all was basically adopted to make wasm catch foreign exceptions, having the multi-language environments in mind.

@RossTate A bit of history - We had a `catch_all` from the very [first version](https://github.com/WebAssembly/exception-handling/blob/master/proposals/old/Exceptions.md) of the proposals. The rationale behind that is 1. we want capability to catch foreign...

@Macil > I'm interested in uncatchable exceptions specifically for the ability to halt everything immediately without the module running cleanup or any other code. I fully expect the module's memory...

I don't think we have a definition of trust domain in the first place. @RossTate, in your scenario, a module may not be able to drop an exception that does...

@RossTate > > What is $X$ and why do we care about those properties in particular? > > I don't think we have a definition of trust domain in the...

- What additional functionalities do these new instructions achieve on top of existing `throw` and `br`? Not sure why we need yet another new instructions. - You stressed that unwinding...

> My primary intent for this post was to help develop conceptual understanding of unwinding, which I thought might be helpful for ongoing discussions. The instructions I use here are...

@RossTate > It seemed pertinent to the discussion in #123, giving a motivation for why to change the design for unwinding. (@aheejin asked me to not give this motivation in...