rust/tests/ui/parser/issues/issue-19398.rs

trait T {
    extern "Rust" unsafe fn foo();
    //~^ ERROR expected `fn`, found keyword `unsafe`
    //~| NOTE expected `fn`
    //~| HELP `unsafe` must come before `extern "Rust"`
    //~| SUGGESTION unsafe extern "Rust"
    //~| NOTE keyword order for functions declaration is `pub`, `default`, `const`, `async`, `unsafe`, `extern`
}

fn main() {}
Fix the ordering of `unsafe` and `extern` in methods This breaks code that looks like this: trait Foo { extern "C" unsafe fn foo(); } impl Foo for Bar { extern "C" unsafe fn foo() { ... } } Change such code to look like this: trait Foo { unsafe extern "C" fn foo(); } impl Foo for Bar { unsafe extern "C" fn foo() { ... } } Fixes #19398. [breaking-change] 2014-11-30 21:33:04 +13:00			`trait T {`
parser: misc small item related improvements & cleanups. 2020-02-01 06:18:10 +01:00			`extern "Rust" unsafe fn foo();`
Improve error message for `extern "C" unsafe fn()` This was handled correctly already for `extern unsafe fn()`. Co-authored-by: Folkert <folkert@folkertdev.nl> 2024-07-26 15:14:05 +02:00			//~^ ERROR expected `fn`, found keyword `unsafe`
			//~\| NOTE expected `fn`
			//~\| HELP `unsafe` must come before `extern "Rust"`
			`//~\| SUGGESTION unsafe extern "Rust"`
			//~\| NOTE keyword order for functions declaration is `pub`, `default`, `const`, `async`, `unsafe`, `extern`
Fix the ordering of `unsafe` and `extern` in methods This breaks code that looks like this: trait Foo { extern "C" unsafe fn foo(); } impl Foo for Bar { extern "C" unsafe fn foo() { ... } } Change such code to look like this: trait Foo { unsafe extern "C" fn foo(); } impl Foo for Bar { unsafe extern "C" fn foo() { ... } } Fixes #19398. [breaking-change] 2014-11-30 21:33:04 +13:00			`}`

			`fn main() {}`