[rust-lang/rust] Range patterns that cover the full range, and unit struct/variant patterns do not "read the value"

### ROOT CAUSE The issue arises because the range pattern `char::MIN..=char::MAX` does not actually read the value of `c`, preventing the compiler from detecting that `c` is uninitialized. This is due to how range patterns are interpreted in Rust, where they are treated as static patterns rather than requiring a read of the variable being matched. ### CODE FIX To fix this, modify the code to ensure the compiler checks the value of `c` by explicitly reading it in the pattern: ```rust fn main() { let c: char; match c { c @ char::MIN..=char::MAX => {} } } ``` This change forces the compiler to read `c`, resulting in the expected compile error when `c` is uninitialized.