rust/tests/ui/parser/issues/issue-87217-keyword-order/wrong-unsafe.stderr

error: expected `fn`, found keyword `unsafe`
  --> $DIR/wrong-unsafe.rs:10:8
   |
LL | extern unsafe fn test() {}
   | -------^^^^^^
   | |      |
   | |      expected `fn`
   | help: `unsafe` must come before `extern`: `unsafe extern`
   |
   = note: keyword order for functions declaration is `pub`, `default`, `const`, `async`, `unsafe`, `extern`

error: aborting due to 1 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 11:10:19 +02:00			error: expected `fn`, found keyword `unsafe`
Update tests. 2024-10-31 11:39:45 +01:00			`--> $DIR/wrong-unsafe.rs:10:8`
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			`\|`
			`LL \| extern unsafe fn test() {}`
			`\| -------^^^^^^`
			`\| \| \|`
			\| \| expected `fn`
			\| help: `unsafe` must come before `extern`: `unsafe extern`
			`\|`
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`
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
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 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 11:10:19 +02:00