rust/src/test/ui/issues/issue-30240.rs

fn main() {
    match "world" { //~ ERROR non-exhaustive patterns: `_`
        "hello" => {}
    }

    match "world" { //~ ERROR non-exhaustive patterns: `_`
        ref _x if false => {}
        "hello" => {}
    }
}
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 15:56:11 -05:00			`fn main() {`
Be honest about being able to list constructors The test change is because we used to treat `&str` like other `&T`s, ie as having a single constructor. That's not quite true though since we consider `&str` constants as atomic instead of refs to `str` constants. 2020-10-19 20:31:21 -05:00			match "world" { //~ ERROR non-exhaustive patterns: `_`
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 15:56:11 -05:00			`"hello" => {}`
			`}`

Be honest about being able to list constructors The test change is because we used to treat `&str` like other `&T`s, ie as having a single constructor. That's not quite true though since we consider `&str` constants as atomic instead of refs to `str` constants. 2020-10-19 20:31:21 -05:00			match "world" { //~ ERROR non-exhaustive patterns: `_`
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 15:56:11 -05:00			`ref _x if false => {}`
			`"hello" => {}`
			`}`
			`}`