rust/tests/ui/pattern/usefulness/issue-30240-rpass.rs

// run-pass
fn main() {
    let &ref a = &[0i32] as &[_];
    assert_eq!(a, &[0i32] as &[_]);

    let &ref a = "hello";
    assert_eq!(a, "hello");

    match "foo" {
        "fool" => unreachable!(),
        "foo" => {},
        ref _x => unreachable!()
    }
}
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 12:18:55 +00:00			`// run-pass`
handle string literals correctly in match checking The root of the problem is that a string literal pattern is essentially of the form `&LITERAL`, in a single block, while match checking wants to split that. To fix that, I added a type field to the patterns in match checking, which allows us to distinguish between a full and split pattern. That file is ugly and needs to be cleaned. However, `trans::_match` calls it, so I think we should delay the cleanup until we kill that. Fixes #30240 2016-06-05 20:56:11 +00:00			`fn main() {`
			`let &ref a = &[0i32] as &[_];`
			`assert_eq!(a, &[0i32] as &[_]);`

			`let &ref a = "hello";`
			`assert_eq!(a, "hello");`

			`match "foo" {`
			`"fool" => unreachable!(),`
			`"foo" => {},`
			`ref _x => unreachable!()`
			`}`
			`}`