Why is this match pattern unreachable when using non-literal patterns?

by

The Rust Programming Language explains how a match expression is processed, emphasis mine:

When the match expression executes, it compares the resulting value against the pattern of each arm, in order.

In your example, max_column is the name of the variable to be bound to, not a constant or an outside variable. When the compiler reaches max_column, any remaining values will be assigned to that match arm, making subsequent arms unreachable.

In your case, you want to make max_column a real constant:

let current_column = 1;
const MAX_COLUMN: i32 = 7;
edge = match current_column {
    0          => Edge::Left,
    MAX_COLUMN => Edge::Right,
    _          => Edge::NotAnEdge
};

Or if that’s not possible, you want a match guard:

let current_column = 1;
let max_column = 7;
edge = match current_column {
    0                    => Edge::Left,
    a if a == max_column => Edge::Right,
    _                    => Edge::NotAnEdge
};

Note that, as a first approximation, a and _ are the same thing in this case! In both cases, the matched variable will be bound to a name (a or _ respectively), but any identifier prefixed with _ is special-cased to be used as an unused variable placeholder.

bluss clarifies and corrects this approximation:

_ is a separate special case, it’s not a variable binding at all, but it is the absence of one! Matching against _x moves the value into _x, _ does no such thing. (The difference is observable.)

More Related Contents:

  1. What are non-lexical lifetimes?
  2. What are Rust’s exact auto-dereferencing rules?
  3. Why is a trait not implemented for a type that clearly has it implemented?
  4. How can I include a module from another file from the same project?
  5. Lifetime error when creating a function that returns a value implementing serde::Deserialize
  6. Passing mutable self reference to method of owned object
  7. Rust proper error handling (auto convert from one error type to another with question mark)
  8. Why is a borrow still held in the else block of an if let?
  9. How to create a static string at compile time
  10. How to call a method when a trait and struct use the same method name?
  11. “expected type parameter, found struct”
  12. How do you set, clear and toggle a single bit in Rust?
  13. Is it possible to declare the type of the variable in Rust for loops?
  14. Lifetime of variables passed to a new thread
  15. How can I co-sort two Vecs based on the values in one of the Vecs?
  16. How can I distinguish between a deserialized field that is missing and one that is null?
  17. Cannot create a generic function that uses a literal zero
  18. How can I store a pattern in a variable in Rust?
  19. How to avoid temporary allocations when using a complex key for a HashMap?
  20. Why does compilation not fail when a member of a moved value is assigned to?
  21. Why does a mutable borrow of a closure through DerefMut not work?
  22. How to switch between Rust toolchains?
  23. Why can Serde not derive Deserialize for a struct containing only a &Path?
  24. Creating a vector of zeros for a specific size
  25. What is the difference between immutable and const variables in Rust?
  26. What is the purpose of the unit type in Rust?
  27. Why does the Rust compiler request I constrain a generic type parameter’s lifetime (error E0309)?
  28. How do I create a HashMap with type erased keys?
  29. How to print structs and arrays?
  30. Can Rust optimise away the bit-wise copy during move of an object someday?

Leave a Comment