Rollup of 7 pull requests

[notriddle]

Successful merges:

• Improve code example for Option::unwrap_or_default #102283 (Improve code example for Option::unwrap_or_default)
• Add a label to struct/enum/union ident name #102314 (Add a label to struct/enum/union ident name)
• rustdoc: merge CSS table rules into .docblock #102319 (rustdoc: merge CSS table rules into .docblock)
• Rustdoc-Json: List impls for primitives #102321 ( Rustdoc-Json: List impls for primitives)
• Document that Display automatically implements ToString #102322 (Document that Display automatically implements ToString)
• rustdoc: give .line-number / .line-numbers meaningful names #102325 (rustdoc: give .line-number / .line-numbers meaningful names)
• rustdoc: Update doc comment for splitn_mut to include mutable in the … #102326 (rustdoc: Update doc comment for splitn_mut to include mutable in the …)

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

[notriddle]

@bors r+ p=7

[bors]

📌 Commit 5ee831c has been approved by notriddle

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-5xd0itc (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-5xd0itc --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_parse/src/parser/item.rs
CONFLICT (content): Merge conflict in compiler/rustc_parse/src/parser/item.rs
Automatic merge failed; fix conflicts and then commit the result.

[bors]

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