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
Currently if we panic in callbacks or in the FFI glue generated for each callback impl, that can cause undefined behaviour as the stack will unwind into C code. It doesn't look like we have a problem right now as panicking works just fine, but once thread::catch_panic() is stabilized (planned for 1.1 stable), we should probably try to catch panics in the FFI glue and safely exit the IUP event loop before re-panicking (or should we prefer to abort?).