4 ms·
As a gopher I never understand why is there so many unwraps in an average rust code. Average Go code has much less panics than Rust has unwraps, which are func
by karel-3d 11mo ago
As a gopher I never understand why is there so many unwraps in an average rust code.
Average Go code has much less panics than Rust has unwraps, which are functionally equivalent.
- richardwhiuk 11mo agoBecause Go silently gives you zero/null instead
- ergocoder 11mo agowhich mean an unexpected behavior could go unnoticed for a long time. I'd prefer a loud crash over that.
- karel-3d 11mo agoWell look at the failure modes in the original article. In the original PHP code, all worked, only it didn't properly check for bots. The new Rust code did a loud crash and took off half of the internet.
- karel-3d 11mo agoIdiomatically, it gives you `err` and you do `if err != nil {return err}`. While in rust you mostly do `.unwrap` and panic. It's not in the type system, but it's idiomatic
- richardwhiuk 11mo agoGet a key from a map and forget to check the error.
- speedgoose 11mo agoThe average golang code segfaults by design.
- selfmodruntime 11mo agoI love Go and write a ton of it. I've had real segfaults quite a lot.