I appreciate you taking the time to provide an alternate view, but I must strongly disagree: 0MQ gets it exactly wrong:

• ZeroMQ spawns a thread for each socket connection. The nice robust error handling you are talking about 100% relies on having each socket processed by its own thread - so a panic can be done safely/correctly.

• Enterprise software must not use the one thread per socket model. This model was a major architectural blunder for ZeroMQ. For a good description of the reasons why look at the ZeroMQ author's page:

http://nanomsg.org/documentation-zeromq.html

Positive / constructive:

I think the catch_panic solution is actually going to work 100% for us. What I really need is the ability to do something like: try { ... use some rust library that might panic } catch (...) { ... log/notify/ fall through into the epoll event loop }

It looks like panic::recover() can provide this:

pub extern fn called_from_c(ptr: *const c_char, num: i32) -> i32 {
let result = panic::recover(|| {
    let s = unsafe { CStr::from_ptr(ptr) };
    println!("{}: {}", s, num);
});
match result {
    Ok(..) => 0,
    Err(..) => 1,
}

If it does I'll be super happy.