> However in Rust, panics cannot be recovered from, there is no way to incept a panic in the current thread.
You definitely can: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html
You definitely can: https://doc.rust-lang.org/std/panic/fn.catch_unwind.html
In the context of the article, this is a somewhat minor point. Because you can't guarantee the recovery from panics, you often code as if you can never recover from panics. And thus, when you write code that can panic (for example, `slice[i]`), it's best to conservatively assume that any such panic won't be recovered from. Still though, the existence of a recovery mechanism can be useful advice in some circumstances: https://docs.rs/regex/1.*/regex/#panics
The broader story here is a knot that is difficult to untangle because 1) people have different values and 2) words mean different things to different people. I tried to untangle some part of it here (although it's more broad than just "panics can or can't be recovered from," it's still all connected): https://blog.burntsushi.net/unwrap/
They can control that panic isn't compiled as abort, but even then, if there's a destructor that can panic, then if it panics during unwinding, it aborts. So even the app developer cannot guarantee to catch all panics.