rust/tests/ui/parser/issues/issue-87217-keyword-order/several-kw-jump.stderr

error: expected one of `extern` or `fn`, found keyword `const`
  --> $DIR/several-kw-jump.rs:9:14
   |
LL | async unsafe const fn test() {}
   | -------------^^^^^
   | |            |
   | |            expected one of `extern` or `fn`
   | help: `const` must come before `async unsafe`: `const async unsafe`
   |
   = note: keyword order for functions declaration is `pub`, `default`, `const`, `async`, `unsafe`, `extern`

error: aborting due to previous error
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			error: expected one of `extern` or `fn`, found keyword `const`
			`--> $DIR/several-kw-jump.rs:9:14`
			`\|`
			`LL \| async unsafe const fn test() {}`
			`\| -------------^^^^^`
			`\| \| \|`
			\| \| expected one of `extern` or `fn`
			\| help: `const` must come before `async unsafe`: `const async unsafe`
			`\|`
Fix invalid keyword order for function declarations 2022-05-02 04:14:43 -05:00			= note: keyword order for functions declaration is `pub`, `default`, `const`, `async`, `unsafe`, `extern`
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
			`error: aborting due to previous error`