Things should not panic a lot, and when I’m going over someone else’s Rust code I will discourage them to use panic at all if it’s socially appropriate. Inasmu

Things should not panic a lot, and when I’m going over someone else’s Rust code I will discourage them to use panic at all if it’s socially appropriate. Inasmuch as I am aware, the correct usage of panic is “there is no way to recover from this without leaving the application in an undefined state”. Not “a file I expected to exist wasn’t there” or “the user gave bad input” or “I didn’t implement this feature yet”. But more like “a cosmic ray must have struck the machine or something, because this ought to be logically impossible.” Or pretty much, if you literally don’t see a mechanism in Rust that can pass an error upwards and the program also cannot continue execution without the result being affected, then you panic. That’s a little stricter than what I understand the official guidance is, but not much. If you have something panicking it should be less “I can’t see what’s going on” and more “thank god it stopped itself so it didn’t write bogus data to production.”