You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're big fans of cxx, but we have one small wish: we'd love to see a different panic handling mode on the ffi boundary. Currently, it causes an abort (through unwind.rs), but we'd prefer a different behavior (controlled by a crate feature, of course): throwing a C++ exception instead. Our software is mission-critical, and we strive to minimize process crashes, preferring to handle issues at the thread level.
Just to clarify, we're not requesting this feature; I'm planning to implement it myself. I'm reaching out to see if this aligns with cxx's plans and if there's interest in reviewing and accepting corresponding pull requests in a reasonable timeline.
While we could fork and change cxx for our needs, we believe this feature could benefit others too. It would be great to have it upstream rather than maintaining a fork indefinitely.
The text was updated successfully, but these errors were encountered:
Thanks a bunch for all your hard work!
We're big fans of cxx, but we have one small wish: we'd love to see a different panic handling mode on the ffi boundary. Currently, it causes an abort (through unwind.rs), but we'd prefer a different behavior (controlled by a crate feature, of course): throwing a C++ exception instead. Our software is mission-critical, and we strive to minimize process crashes, preferring to handle issues at the thread level.
Just to clarify, we're not requesting this feature; I'm planning to implement it myself. I'm reaching out to see if this aligns with cxx's plans and if there's interest in reviewing and accepting corresponding pull requests in a reasonable timeline.
While we could fork and change cxx for our needs, we believe this feature could benefit others too. It would be great to have it upstream rather than maintaining a fork indefinitely.
The text was updated successfully, but these errors were encountered: