`crate::io::Result` → `io::Result` in most places by tbu- · Pull Request #149778 · rust-lang/rust

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

tbu- · 2025-12-08T17:26:01Z

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

rustbot · 2025-12-08T17:26:07Z

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- · 2025-12-08T20:26:09Z

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

bors · 2025-12-09T09:47:54Z

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

ChrisDenton · 2025-12-09T10:00:43Z

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 · 2025-12-13T22:23:49Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-13T23:08:48Z

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

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

bors · 2025-12-15T23:21:49Z

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

Mark-Simulacrum · 2025-12-28T19:53:08Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-28T20:41:27Z

💔 Test for fe243a2 failed: CI. Failed jobs:

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

tbu- · 2025-12-29T04:16:12Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T04:16:14Z

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

Mark-Simulacrum · 2025-12-29T12:54:16Z

@bors try jobs=dist-various-*

rust-bors · 2025-12-29T12:54:19Z

🔒 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:

git checkout pr_crate_io_result(switch to your branch)
git fetch upstream HEAD(retrieve the latest base branch)
git rebase upstream/HEAD -p(rebase on top of it)
Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
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 · 2025-12-29T13:28:51Z

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

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

rustbot · 2025-12-29T14:10:01Z

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- · 2025-12-29T14:11:04Z

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

Mark-Simulacrum · 2025-12-30T23:54:48Z

@bors try jobs=dist-various-*

`crate::io::Result` → `io::Result` in most places try-job: dist-various-*

rust-bors · 2025-12-31T01:19:55Z

☀️ Try build successful (CI)
Build commit: 444008e (444008ec255612dcd4eea09f52e177e80744d918, parent: 0e8999942552691afc20495af6227eca8ab0af05)

Mark-Simulacrum · 2026-01-01T00:15:47Z

@bors r+

bors · 2026-01-01T00:15:50Z

📌 Commit 440bf4d has been approved by Mark-Simulacrum

It is now in the queue for this repository.

…uwer Rollup of 4 pull requests Successful merges: - #149778 (`crate::io::Result` → `io::Result` in most places) - #150264 (split up tracking issue for target feature feature gates) - #150548 (`region_scope_tree`: Rewrite a `loop` as tail recursion) - #150555 (Enable thumb interworking on ARMv7A/R and ARMv8R bare-metal targets) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #149778 - tbu-:pr_crate_io_result, r=Mark-Simulacrum `crate::io::Result` → `io::Result` in most places I don't know why many places refer to the type as `crate::io::Result` when `crate::io` is already imported.

bors · 2026-01-01T07:52:34Z

⌛ Testing commit 440bf4d with merge 6e48b44...

rustbot assigned Mark-Simulacrum Dec 8, 2025