Inconsistent syntax between unsafe async fn and async fn unsafe

[topecongiro]

There is an inconsistency in the ordering of async and unsafe keywords that come before the fn signature. A plain function signature requires async unsafe fn, whereas a method signature requires unsafe async fn:

#![feature(async_await)]

struct A;

pub async unsafe fn thing() -> Result<(), ()> {
    unimplemented!()
}

impl A {
    pub unsafe async fn thing(&mut self) -> Result<(), ()> {
        unimplemented!()
    }
}

fn main() {}

• A related PR: Swap order of unsafe async fn to async unsafe fn #61319.
• A link to the playground
• An original issue in rustfmt: unsafe async fn -> async unsafe fn + error rustfmt#3662

[Centril]

Ouch seems I forgot about implementations in #61319.
I assumed it was the same code path... :(

Thanks for reporting this!

(The right order is async unsafe fn)

[Centril]

I have a fix in #62241.