os-rust/src/test/ui/issues/issue-28433.rs

// compile-flags: -Z continue-parse-after-error

enum bird {
    pub duck,
    //~^ ERROR: expected identifier, found keyword `pub`
    //~| ERROR: expected
    goose
}


fn main() {
    let y = bird::goose;
}
fix compile-fail and parse-fail tests by blindly opting back into parser recovery (so that expected errors match up) I'm opting into parser recovery in all these cases out of expediency, not because the error messages you get with recovery enabled are actually all that usable in all cases listed. 2016-03-26 01:36:03 +01:00			`// compile-flags: -Z continue-parse-after-error`

libsyntax: forbid visibility modifiers for enum variants fixes #28433 2015-09-16 19:35:33 +03:00			`enum bird {`
Fix test expectations because of #28439 2015-09-17 12:47:03 +03:00			`pub duck,`
			//~^ ERROR: expected identifier, found keyword `pub`
`struct` pattern parsing and diagnostic tweaks - Recover from struct parse error on match and point out missing match body. - Point at struct when finding non-identifier while parsing its fields. - Add label to "expected identifier, found {}" error. 2018-01-06 14:43:20 -08:00			`//~\| ERROR: expected`
libsyntax: forbid visibility modifiers for enum variants fixes #28433 2015-09-16 19:35:33 +03:00			`goose`
Disallow importing private items resolve wasn't checking that a `use` referred to a public item. r=brson 2012-11-29 12:08:40 -08:00			`}`


			`fn main() {`
libsyntax: forbid visibility modifiers for enum variants fixes #28433 2015-09-16 19:35:33 +03:00			`let y = bird::goose;`
Disallow importing private items resolve wasn't checking that a `use` referred to a public item. r=brson 2012-11-29 12:08:40 -08:00			`}`