Part of the resolution to rust-lang#105107

Part of the resolution to rust-lang#105107

Part of the resolution to rust-lang#105107

Update LLVM submodule

Fixes rust-lang#105626.

Lint against `Iterator::map` receiving a callable that returns `()`

Close rust-lang#106991

…or-auto, r=lcnr

Treat `str` as containing `[u8]` for auto trait purposes

Wanted to gauge `@rust-lang/lang` and `@rust-lang/types` teams' thoughts on treating `str` as "containing" a `[u8]` slice for auto-trait purposes.

`@dtolnay` brought this up in rust-lang#13231 (comment) as a blocker for future `str` type librarification, and I think it's both a valid concern and very easy to fix. I'm interested in actually doing that `str` type librarification (rust-lang#107939), but this probably should be considered in the mean time regardless of that PR.

r? types for the impl, though this definitely needs an FCP.

…-107918, r=notriddle

Add regression test for rust-lang#107918

Fixes rust-lang#107918.

r? `@notriddle`

…anicked, r=estebank

make "proc macro panicked" translatable

…r=GuillaumeGomez

docs/test: add UI test and docs for `E0476`

Final undocumented error code. Not entirely sure about wording in the docs.

Part of rust-lang#61137.

r? `@compiler-errors`

cc `@compiler-errors`

…er-errors

Add known-bug tests for a few I-unsound issues

Just a few commits to push rust-lang#105107 forward.

r? `@jackh726`

…solved, r=compiler-errors

Do not lint ineffective unstable trait impl for unresolved trait

… r=compiler-errors

Complete migrating `ast_passes` to derive diagnostics

cc rust-lang#100717

`@rustbot` label +A-translation