Add #[inline] to RawWaker::new

[tmiasko]

RawWaker::new is used when creating a new waker or cloning an existing one,
for example as in code below. The RawWakerVTable::new can be const evaluated,
but RawWaker::new itself cannot since waker pointer is not known at compile
time. Add #[inline] to avoid overhead of a function call.

unsafe fn clone_waker<W: Wake + Send + Sync + 'static>(waker: *const ()) -> RawWaker {
    unsafe { Arc::incr_strong_count(waker as *const W) };
    RawWaker::new(
        waker as *const (),
        &RawWakerVTable::new(clone_waker::<W>, wake::<W>, wake_by_ref::<W>, drop_waker::<W>),
    )
}

[rust-highfive]

r? @LukasKalbertodt

(rust_highfive has picked a reviewer for you, use r? to override)

[KodrAus]

Since this method is const is there a reason to inline it?

[tmiasko]

The data pointer is usually different for each task and determined at runtime,
so it generally cannot be const evaluated. In contrast to say RawWakerVTable::new
down below.

This is something I noticed while examining the perf report.

[bors]

☔ The latest upstream changes (presumably #73265) made this pull request unmergeable. Please resolve the merge conflicts.

[LukasKalbertodt]

Seems reasonable.

@bors r+ rollup=always

[bors]

📌 Commit 0a51a9f has been approved by LukasKalbertodt

[JohnTitor]

I think this may affect perf and shouldn't be rollup=always but rollup=never?

[LukasKalbertodt]

Thanks for catching that. I forgot about it. Can I simply change it after approving it like this?

@bors rollup=never

[JohnTitor]

Can I simply change it after approving it like this?

Yep, it works.

[bors]

⌛ Testing commit 0a51a9f with merge 4cca950...

[bors]

☀️ Test successful - checks-actions, checks-azure
Approved by: LukasKalbertodt
Pushing 4cca950 to master...