rust/tests/ui/parser/issues/issue-87217-keyword-order/const-async-const.rs

// edition:2018

// Test that even when `const` is already present, the proposed fix is to remove the second `const`

const async const fn test() {}
//~^ ERROR expected one of `extern`, `fn`, or `unsafe`, found keyword `const`
//~| NOTE expected one of `extern`, `fn`, or `unsafe`
//~| HELP `const` already used earlier, remove this one
//~| NOTE `const` first seen here
Better message for invalid keyword placement in fn After this commit, `unsafe async fn ...` now suggests the `async unsafe` fix instead of misunderstanding the issue. This is not perfect for repeated keywords (`const async const`) and for keywords that are misplaced after `extern "some abi"` because of the way `check_fn_font_matter` works, but changing it breaks so many tests and diagnostics it has been judged too high a cost for this PR. 2021-08-02 04:10:19 -05:00			`// edition:2018`

Update test to new error message 2021-10-24 08:11:11 -05:00			// Test that even when `const` is already present, the proposed fix is to remove the second `const`
Better message for invalid keyword placement in fn After this commit, `unsafe async fn ...` now suggests the `async unsafe` fix instead of misunderstanding the issue. This is not perfect for repeated keywords (`const async const`) and for keywords that are misplaced after `extern "some abi"` because of the way `check_fn_font_matter` works, but changing it breaks so many tests and diagnostics it has been judged too high a cost for this PR. 2021-08-02 04:10:19 -05:00
			`const async const fn test() {}`
			//~^ ERROR expected one of `extern`, `fn`, or `unsafe`, found keyword `const`
			//~\| NOTE expected one of `extern`, `fn`, or `unsafe`
Update test to new error message 2021-10-24 08:11:11 -05:00			//~\| HELP `const` already used earlier, remove this one
			//~\| NOTE `const` first seen here