rust/tests/ui/issues/issue-18464.rs

//@ run-pass
#![deny(dead_code)]

const LOW_RANGE: char = '0';
const HIGH_RANGE: char = '9';

fn main() {
    match '5' {
        LOW_RANGE..=HIGH_RANGE => (),
        _ => ()
    };
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`//@ run-pass`
Constants used in range patterns should not be considered unused 2014-10-31 00:19:01 +01:00			`#![deny(dead_code)]`

			`const LOW_RANGE: char = '0';`
			`const HIGH_RANGE: char = '9';`

			`fn main() {`
			`match '5' {`
migrate codebase to `..=` inclusive range patterns These were stabilized in March 2018's #47813, and are the Preferred Way to Do It going forward (q.v. #51043). 2018-05-28 19:42:11 -07:00			`LOW_RANGE..=HIGH_RANGE => (),`
Constants used in range patterns should not be considered unused 2014-10-31 00:19:01 +01:00			`_ => ()`
			`};`
			`}`