That's very true.
Do you think I should have written it differently? I might want to add a clause in the caveats section at the very least.
Do you think I should have written it differently? I might want to add a clause in the caveats section at the very least.
I wouldn't say "allowed" to segfault. :P The behavior you're referring to is currently due to a deficiency in LLVM for non-Windows platforms. Here's the bug on the Rust repo tracking it: https://github.com/rust-lang/rust/issues/16012 Its resolution is long-awaited, to say the least, but it requires someone proficient with LLVM to do the legwork...
> an in-rust panic might be recoverable?
Anytime you're writing an interface where code is going to be calling into Rust via C FFI, you ought to be using https://doc.rust-lang.org/std/panic/fn.catch_unwind.html , which is specifically intended to prevent panics from crossing FFI boundaries.
How do you expect a stack overflow to unwind? I have difficulty imagining the implementation
As kibwen says, the ways this can happen currently are bugs. They'll be fixed.