This is handled similar to closures

The closure handling code is changed slightly to avoid allocation
when THIR building failed.

MIR unsafety checking requires this to be valid

All bodies are unsafe checked anyway. Current MIR unsafeck also just
returns for closures.

…_codegen_ssa

… being available

… of relying on the span making it obvious

…lable

…nostics

Synthesize a more accurate span and use verbose suggestion output to
make the message clearer.

Fix rust-lang#104838.

…i-obk

Allow unsafe through inline const

Handle similar to closures.

Address rust-lang#104087 (comment)

Note that this PR does not fix the issue for `unsafe { [0; function_requiring_unsafe()] }`. This is fundamentally unfixable for MIR unsafeck IMO.

This PR also does not fix unsafety checking for inline const in pattern position. It actually breaks it, allowing unsafe functions to be used in inline const in pattern position without unsafe blocks. Inline const in pattern position is not visible in MIR so ignored by MIR unsafety checking (currently it is also not checked by borrow checker, which is the reason why it's considered an incomplete feature).

`@rustbot` label: +T-lang +F-inline_const

…tebank

Move some codegen-y methods from `rustc_hir_analysis::collect` -> `rustc_codegen_ssa`

Unclear if they should live here, but they seem codegen-y enough, and `rustc_hir_analysis::collect` is extremely long, so it should probably lose some methods.

Support #[track_caller] on async closures

Follow up on rust-lang#105180

r? ```@compiler-errors```
cc ```@cjgillot```

…er-errors

Change pattern borrowing suggestions to be verbose and remove invalid suggestion

Synthesize a more accurate span and use verbose suggestion output to
make the message clearer.

Do not suggest borrowing binding in pattern in let else. Fix rust-lang#104838.

…tebank

Make some diagnostics not depend on the source of what they reference being available

r? `@estebank`

follow up to rust-lang#104449

…iler-errors

Small doc fixes

r? `@compiler-errors`

…davidtwco

Don't require owned data in `MaybeStorageLive`

Small improvement that avoids a clone. I don't expect this to have any noticeable perf effects, but better to have it than not to.

r? ``@tmiasko``