Rollup of 6 pull requests

[Centril]

Successful merges:

• Future-proof MIR for dedicated debuginfo. #56278 (Future-proof MIR for dedicated debuginfo.)
• Stabilize futures_api #59739 (Stabilize futures_api)
• Fix dark css rule #59822 (Fix dark css rule)
• Update cargo, books #60180 (Update cargo, books)
• Temporarily accept [i|u][32|size] suffixes on a tuple index and warn #60186 (Temporarily accept [i|u][32|size] suffixes on a tuple index and warn)
• Don't generate unnecessary rmeta files. #60190 (Don't generate unnecessary rmeta files.)

Failed merges:

r? @ghost

[Centril]

@bors r+ p=6

[bors]

📌 Commit e74cacc has been approved by Centril

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

warning: Cannot merge binary files: Cargo.lock (HEAD vs. heads/homu-tmp)
Auto-merging Cargo.lock
CONFLICT (content): Merge conflict in Cargo.lock
Automatic merge failed; fix conflicts and then commit the result.