rust/tests/ui/parser/issues/issue-21475.rs

// run-pass
#![allow(unused_imports, overlapping_range_endpoints)]
// pretty-expanded FIXME #23616

use m::{START, END};

fn main() {
    match 42 {
        m::START..=m::END => {},
        0..=m::END => {},
        m::START..=59 => {},
        _  => {},
    }
}

mod m {
  pub const START: u32 = 4;
  pub const END:   u32 = 14;
}
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 07:18:55 -05:00			`// run-pass`
Rename the `overlapping_patterns` lint to `overlapping_range_endpoints` 2020-10-22 12:34:00 -05:00			`#![allow(unused_imports, overlapping_range_endpoints)]`
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 15:13:15 -05:00			`// pretty-expanded FIXME #23616`

FIX #21475: Interval match patterns won't parse namespace specifiers correctly 2015-01-22 13:56:27 -06:00			`use m::{START, END};`

			`fn main() {`
Remove integer suffixes where the types in compiled code are identical. 2015-03-03 02:42:26 -06:00			`match 42 {`
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 21:42:11 -05:00			`m::START..=m::END => {},`
			`0..=m::END => {},`
			`m::START..=59 => {},`
FIX #21475: Interval match patterns won't parse namespace specifiers correctly 2015-01-22 13:56:27 -06:00			`_ => {},`
			`}`
			`}`

			`mod m {`
			`pub const START: u32 = 4;`
			`pub const END: u32 = 14;`
			`}`