rust/src/test/ui/parser/issues/issue-24780.rs

// Verify that '>' is not both expected and found at the same time, as it used
// to happen in #24780. For example, following should be an error:
// expected one of ..., `>`, ... found `>`.

fn foo() -> Vec<usize>> { //~ ERROR expected one of `!`, `+`, `::`, `;`, `where`, or `{`, found `>`
    Vec::new()
}

fn main() {}
Breaking tokens into pieces should behave similar to Parser::bump. Previously when breaking tokens into smaller pieces, the replace_token function have been used. It replaced current token and updated span information, but it did not clear the list of expected tokens, neither did it update remaining info about last token. This could lead to incorrect error message, like one described in the issue #24780: expected one of ... `>` ... found `>` 2016-02-06 11:42:17 -06:00			`// Verify that '>' is not both expected and found at the same time, as it used`
			`// to happen in #24780. For example, following should be an error:`
Revert invalid `fn` return type parsing change Fix #78507. 2020-10-29 10:26:42 -05:00			// expected one of ..., `>`, ... found `>`.
Breaking tokens into pieces should behave similar to Parser::bump. Previously when breaking tokens into smaller pieces, the replace_token function have been used. It replaced current token and updated span information, but it did not clear the list of expected tokens, neither did it update remaining info about last token. This could lead to incorrect error message, like one described in the issue #24780: expected one of ... `>` ... found `>` 2016-02-06 11:42:17 -06:00
Revert invalid `fn` return type parsing change Fix #78507. 2020-10-29 10:26:42 -05:00			fn foo() -> Vec<usize>> { //~ ERROR expected one of `!`, `+`, `::`, `;`, `where`, or `{`, found `>`
Breaking tokens into pieces should behave similar to Parser::bump. Previously when breaking tokens into smaller pieces, the replace_token function have been used. It replaced current token and updated span information, but it did not clear the list of expected tokens, neither did it update remaining info about last token. This could lead to incorrect error message, like one described in the issue #24780: expected one of ... `>` ... found `>` 2016-02-06 11:42:17 -06:00			`Vec::new()`
			`}`
Tweak invalid `fn` header and body parsing * Recover empty `fn` bodies when encountering `}` * Recover trailing `>` in return types * Recover from non-type in array type `[<BAD TOKEN>; LEN]` 2020-10-25 16:20:44 -05:00
			`fn main() {}`