Re:Pretty Rust backtraces in raw terminal mode
by 1letterunixname on Friday February 24, 2023 @05:22PM
(#34930979)
You can easily make lots of fragile Rust code by poor error handling that cause shitty panics like "Some(2) != None" and suppressing backtraces for even more obscurity. Good backtraces need to be human- and machine-readable. Ideally, you'd throw (pun intended) panic objects (not backtraces) as structured data in individual files. Anyone who gets into reinventing flat log rotation management at scale is holding it wrong.
[ Parent
| on HN ]
There are no comments on this comment yet.