Listing 6-6: A match that only cares about executing code when the value is Some(3)

    We want to do something with the Some(3) match but do nothing with any other Some<u8> value or the None value. To satisfy the match expression, we have to add _ => () after processing just one variant, which is a lot of boilerplate code to add.

    Instead, we could write this in a shorter way using if let. The following code behaves the same as the in Listing 6-6:

    Using if let means less typing, less indentation, and less boilerplate code. However, you lose the exhaustive checking that match enforces. Choosing between match and if let depends on what you’re doing in your particular situation and whether gaining conciseness is an appropriate trade-off for losing exhaustive checking.

    In other words, you can think of if let as syntax sugar for a match that runs code when the value matches one pattern and then ignores all other values.

    We can include an else with an if let. The block of code that goes with the else is the same as the block of code that would go with the _ case in the expression that is equivalent to the if let and else. Recall the Coin enum definition in Listing 6-4, where the Quarter variant also held a UsState value. If we wanted to count all non-quarter coins we see while also announcing the state of the quarters, we could do that with a match expression like this:

    If you have a situation in which your program has logic that is too verbose to express using a match, remember that if let is in your Rust toolbox as well.

    We’ve now covered how to use enums to create custom types that can be one of a set of enumerated values. We’ve shown how the standard library’s Option<T> type helps you use the type system to prevent errors. When enum values have data inside them, you can use match or if let to extract and use those values, depending on how many cases you need to handle.

    Your Rust programs can now express concepts in your domain using structs and enums. Creating custom types to use in your API ensures type safety: the compiler will make certain your functions get only values of the type each function expects.