crate::io::Result → io::Result in most places

[tbu-]

I don't know why many places refer to the type as crate::io::Result when crate::io is already imported.

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[tbu-]

How do I verify that I haven't broken all of these targets that the CI doesn't check?

[bors]

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

[ChrisDenton]

How do I verify that I haven't broken all of these targets that the CI doesn't check?

Something like:

./x build library/std --target x86_64-fortanix-unknown-sgx,x86_64-unknown-hermit

[Mark-Simulacrum]

@bors try jobs=dist-various-*

[rust-bors]

💔 Test for 866d786 failed: CI. Failed jobs:

• try - dist-various-2 (web logs, enhanced plaintext logs)

[bors]

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

[Mark-Simulacrum]

@bors try jobs=dist-various-*

[rust-bors]

💔 Test for fe243a2 failed: CI. Failed jobs:

• try - dist-various-2 (web logs, enhanced plaintext logs)

[tbu-]

@bors try jobs=dist-various-*

[rust-bors]

@tbu-: 🔑 Insufficient privileges: not in try users

[Mark-Simulacrum]

@bors try jobs=dist-various-*

[rust-bors]

🔒 Merge conflict

This pull request and the base branch diverged in a way that cannot
be automatically merged. Please rebase on top of the latest base
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 pr_crate_io_result (switch to your branch)
2. git fetch upstream HEAD (retrieve the latest base branch)
3. git rebase upstream/HEAD -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 pr_crate_io_result --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.

[bors]

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

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[tbu-]

@Mark-Simulacrum Can you delegate the ability to @bors try jobs=dist-various-*? If not, consider this a request for the command.