rust/tests/ui/async-await/no-async-const.stderr

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

error: aborting due to previous error
parser: fuse free `fn` parsing together. 2020-01-30 13:02:06 +01:00			error: expected one of `extern`, `fn`, or `unsafe`, found keyword `const`
compiletest: error if `compile-fail` header in ui test. 2020-02-02 01:05:53 -05:00			`--> $DIR/no-async-const.rs:4:11`
Add more tests for async/await 2019-06-24 17:48:21 -07:00			`\|`
			`LL \| pub async const fn x() {}`
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 11:10:19 +02:00			`\| ------^^^^^`
			`\| \| \|`
			\| \| expected one of `extern`, `fn`, or `unsafe`
			\| help: `const` must come before `async`: `const async`
			`\|`
Fix invalid keyword order for function declarations 2022-05-02 18:14:43 +09:00			= note: keyword order for functions declaration is `pub`, `default`, `const`, `async`, `unsafe`, `extern`
Add more tests for async/await 2019-06-24 17:48:21 -07:00
			`error: aborting due to previous error`