,
8 tweets,
2 min read
Read on Twitter
Spending the weekend rewriting some early Rust projects and OMG some of this error handling is cringy. I've learned a lot about error handling in #rustlang since:
match & if let statements are easily nested into infinity - this style puts the "successful path" first, but its hard to debug and folks coming from other langs will curse you.
A lot of matches with if/else nesting can be eliminated with match guards -- easy to forget they exist, but they are much more concise.
Result and Option type have many combination & map methods that can reduce/eliminate branching code: unwrap_or_else, and_then, map_err, etc. This can be abused, but dem epic one-liners tho.
Result is_ok & is_err methods reduce the result to a bool. If you don't care about the value of Ok/Err, it concisely frees you from types. Option similarly has is_some & is_none.
Options can be turned into a Result type using ok_or/ok_or_else methods, allowing for the ? postfix, further reducing boilerplate.
Option and Result have an iter method. Combined with filter or filter_map, you can apply specific value validation in the same statement, reducing need for mutability in many places.
Some of this stuff would be better served by a code example. Probably worth a dev.to post 🤯
