Re:Practical nil panic detection for Go
by mariopt on Saturday November 18, 2023 @12:50PM
(#38322233)
Rust is a lot better in this aspect, but this is a symptom of not having proper code review and standards.
Do not forget that in some scenarios using unwrap is totally fine if a panic is acceptable.
The same could be said for javascript: How many time have we not wrapped JSON.parse inside a try catch? More than we would like to admit.
Really appreciate Rust “forces” you to handles all execution paths.
[ Parent
| on HN ]
My link is to the rust repo on github. Does the Rust project not have proper standards for Rust code?
Re:Practical nil panic detection for Go
by Philpax on Saturday November 18, 2023 @01:38PM
(#38322869)
> Do not forget that in some scenarios using unwrap is totally fine if a panic is acceptable.
Looking through the first few pages, most of these panics are easy to audit, and are infallible or in contexts where it doesn't matter (internal tooling, etc). That's a pretty stark difference to every single reference being a potential landmine.
Yes, you are probably less likely to get a panic caused by a nil reference in Rust than in Go. My point is that the equivalent software written in Rust (or most other languages with option types) would probably have had at least some of these very same bugs.