Currently ICEs because we buffer it with NodeId of the missing lifetime,
so it ends up not getting emitted

…for lint buffering

…nnotations

So that you know it's about linting and not about correctness.

Yes, it is also inverted now.

from `LateResolutionVisitor` to `LifetimeRes::Static`

…e-const-can-only-call-stable-const

… by rust-lang#126187

According to comments:
rust-lang#128084 (comment)
https://github.com/rust-lang/rust/pull/126187/files#r1634897691

…gillot

Lint that warns when an elided lifetime ends up being a named lifetime

As suggested in rust-lang#48686 (comment)

Fixes rust-lang#48686

## TODO:
- [ ] Crater run?

## Questions:
- [ ] Should we separate the `'static` case and the named lifetime parameter case?
- [ ] Should this be `Allow` or `Warn` by default?
- [ ] Should this be gated behind an edition?

## Future improvemetns:
- [ ] Add machine-applicable suggestions

`@rustbot` label A-lint

…, r=lcnr

Use subtyping for `UnsafeFnPointer` coercion, too

I overlooked this in rust-lang#129059, which changed MIR typechecking to use subtyping for other fn pointer coercions.

Fixes rust-lang#129285

Fixing span manipulation and indentation of the suggestion introduced by rust-lang#126187

According to comments:
rust-lang#128084 (comment)
https://github.com/rust-lang/rust/pull/126187/files#r1634897691

…, r=tgross35

gitignore: ignore ICE reports regardless of directory

Quite often when working on compiler I end up running into ICEs during the standard library compilation.

These ICEs generate reports in `/library/` and not at the root of the repo, so they aren't `gitignore`d.

I finally ended up committing one today, by accident: rust-lang#129487 (comment)

…fmease

Remove redundant flags from `lower_ty_common` that can be inferred from the HIR

...and then get rid of `lower_ty_common`.

r? `@fmease` or re-roll if you're busy!

…r=compiler-errors

Removes dead code from the compiler

Detected by rust-lang#128637

…er-errors

add back test for stable-const-can-only-call-stable-const

This got accidentally removed in rust-lang#128596 (file `tests/ui/internal/internal-unstable-const.rs`). The test has little to do with "allow internal unstable" though, so add it in a file that already tests various const stability things.

Also tweak the help that suggests to add `rustc_allow_const_fn_unstable` to make it clear that this needs team approval, since it is a fairly big gun.

Avoid taking reference of &TyKind

It's already a ref anyways. Just a tiny cleanup here.