@James Munns (Embedded), @Josh Triplett (FFI), and @Alex Crichton (WASM) -- we're trying to resolve in #64224 whether it's worth trying to bring the code size of catch_unwind down even further. It sounds like at least Servo has no data showing that the performance improvement such a change could bring is worth it, but I'm wondering if any of you are aware if your domains would benefit from help here.
If you have thoughts here I'd appreciate a comment on that issue or I'm happy to discuss here as well!
cc @nikomatsakis as well, I'm not sure who is leading the FFI unwinding effort but they might be interested in this as well
I will leave a comment when back from break
@simulacrum I believe @Kyle Strand is leading ffi unwind with niko.
As a bit of a follow up we've since ended up investing some time with @Amanieu and should have reached parity with C++.
Where can I learn more about the follow-up work that was done?
To follow up from this I don't think catch_unwind affects wasm at all right now since wasm is always panic=abort