Rollup of 9 pull requests

[compiler-errors]

Successful merges:

• Stabilize arbitrary_enum_discriminant, take 2 #95710 (Stabilize arbitrary_enum_discriminant, take 2)
• Enable varargs support for calling conventions other than C or cdecl  #97971 (Enable varargs support for calling conventions other than C or cdecl )
• privacy: Rename "accessibility levels" to "effective visibilities" #102233 (privacy: Rename "accessibility levels" to "effective visibilities")
• Name the impl Trait in region bound suggestions #103416 (Name the impl Trait in region bound suggestions)
• Use &self instead of &mut self for cast methods #103533 (Use &self instead of &mut self for cast methods)
• Remove rustc_driver::set_sigpipe_handler() #103536 (Remove rustc_driver::set_sigpipe_handler())
• Pinning tests for some macro_rules! errors discussed in the lang meeting #103542 (Pinning tests for some macro_rules! errors discussed in the lang meeting)
• Update books #103543 (Update books)
• llvm-16: Don't initialize removed legacy passes #103549 (llvm-16: Don't initialize removed legacy passes)

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[compiler-errors]

@bors rollup=never p=7

[JohnTitor]

@bors r=compiler-errors

[bors]

📌 Commit 1114be0 has been approved by compiler-errors

It is now in the queue for this repository.

[compiler-errors]

Of course I forgot the most important part. Thanks @JohnTitor.

[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-objjnyh (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-objjnyh --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

CONFLICT (modify/delete): src/test/ui/privacy/access_levels.stderr deleted in heads/homu-tmp and modified in HEAD. Version HEAD of src/test/ui/privacy/access_levels.stderr left in tree.
CONFLICT (modify/delete): src/test/ui/privacy/access_levels.rs deleted in heads/homu-tmp and modified in HEAD. Version HEAD of src/test/ui/privacy/access_levels.rs left in tree.
Removing src/test/ui/parser/tag-variant-disr-non-nullary.stderr
Removing src/test/ui/parser/tag-variant-disr-non-nullary.rs
Removing src/test/ui/parser/issues/issue-17383.stderr
Removing src/test/ui/parser/issues/issue-17383.rs
Removing src/test/ui/enum-discriminant/feature-gate-arbitrary_enum_discriminant.stderr
Removing src/test/ui/enum-discriminant/feature-gate-arbitrary_enum_discriminant.rs
Removing src/doc/unstable-book/src/language-features/arbitrary-enum-discriminant.md
Auto-merging compiler/rustc_resolve/src/effective_visibilities.rs
CONFLICT (content): Merge conflict in compiler/rustc_resolve/src/effective_visibilities.rs
Auto-merging compiler/rustc_privacy/src/lib.rs
CONFLICT (content): Merge conflict in compiler/rustc_privacy/src/lib.rs
Auto-merging compiler/rustc_middle/src/middle/privacy.rs
CONFLICT (content): Merge conflict in compiler/rustc_middle/src/middle/privacy.rs
Automatic merge failed; fix conflicts and then commit the result.

[bors]

☔ The latest upstream changes (presumably #103158) made this pull request unmergeable. Please resolve the merge conflicts.