Semantically, those who want to make those
extern "C" Rust definitions
abort can already do so by just using
catch_unwind, so while we could add a "proc macro" that does it for them, it shouldn't be necessary for an MVP
The MVP could just be "unwinding from
extern "C" is ok, and for
extern "C" declarations only there is a
#[ffi_no_unwind] attribute that you can use."
The "unwinding from
extern "C" is ok" guarantee could be worded carefully, to say that it unwinds with a platform unwind, meaning that we on paper "translate" a Rust unwind to a platform unwind, so that this does not stabilize nor constrain the Rust unwind implementation details.