`return` statements in inlined functions just get moved over and try to return out of the outer function + generic types are discarded

title,

code example

fn none<T>() -> Option<T> {
    return None;
}

pub fn main() {
    let a = none::<u32>();
}

• inlining the none function replaces it with let a = { return None; };, which tries to return None in main
• the generic type param T of none was first known to be u32, to preserve this information (and not end up with "type annotations needed for Option<T>") let a = None::<u32>; would work

rust-analyzer version: 0.4.1625-standalone

rustc version: rustc 1.71.1 (eb26296b5 2023-08-03)

relevant settings: none

Start by reproducing the reported Rust example with rust-analyzer's function-inlining feature. Trace the inlining implementation and its existing tests, if present; done means an inlined return remains valid within the replacement expression and the known generic type is preserved without a type-inference error.