Rollup of 6 pull requests

[matthiaskrgr]

Successful merges:

• Name explicit registers in conflict register errors for inline assembly #117912 (Name explicit registers in conflict register errors for inline assembly)
• Add never_patterns feature gate #118157 (Add never_patterns feature gate)
• Suggest let or == on typo'd let-chain #118191 (Suggest let or == on typo'd let-chain)
• also add is_empty to const raw slices #118231 (also add is_empty to const raw slices)
• Pretty print Fn<(..., ...)> trait refs with parentheses (almost) always #118268 (Pretty print Fn<(..., ...)> trait refs with parentheses (almost) always)
• Print list of missing target features when calling a function with target features outside an unsafe block #118333 (Print list of missing target features when calling a function with target features outside an unsafe block)

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[matthiaskrgr]

@bors r+ rollup=never p=6

[bors]

📌 Commit e3970cb has been approved by matthiaskrgr

It is now in the queue for this repository.

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout rollup-9xtgmwm (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self rollup-9xtgmwm --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

Auto-merging compiler/rustc_lint/src/unused.rs
Auto-merging compiler/rustc_infer/src/infer/error_reporting/mod.rs
CONFLICT (content): Merge conflict in compiler/rustc_infer/src/infer/error_reporting/mod.rs
Auto-merging compiler/rustc_hir/src/hir.rs
Auto-merging compiler/rustc_feature/src/unstable.rs
Auto-merging compiler/rustc_ast_lowering/src/pat.rs
Auto-merging compiler/rustc_ast/src/ast.rs
Automatic merge failed; fix conflicts and then commit the result.