Ben L. Titzer
Ben L. Titzer
Also note: there is an item on the August 1st meeting agenda to discuss EH. https://github.com/WebAssembly/meetings/blob/main/main/2023/CG-08-01.md
Slides from today's meeting: https://docs.google.com/presentation/d/15LAJ7VfE_68mgolMgeg9AEJbrrEGoNkEOXhG1J6_5W0/edit#slide=id.p
I think our best bet to get `exnref` into this proposal is to put reasonable restrictions on it so that it can be effectively flattened when compiled in AOT mode....
@rosstate Unfortunately we are in a constraint system that does not admit significant redesign of the exception handling mechanism, so we'll have to stay focused on a very minimal change...
Hi Keith, The original issue above had a list of problems that the lack of `exnref` and the lexical rethrow construct give rise to. After many discussions with toolchain implementers,...
Should we also consider a case that unpacks and drops the exnref, such as `catch_drop`? I've argued elsewhere that that would allow engines to elide the package allocation for such...
@eqrion A flag for each catch sounds fine, and the `catch_all` that drops sounds fine as well.
Agree that flags byte is probably the best bet.
Catches are part of `try_table`; in fact, they are actually immediates of a `try_table` instruction, so they don't have a separate "opcode".
In V8 we've recently renamed the _WASMEXP_ object to simply "Wasm".