Skip to content

Replace try_reserve_exact with try_with_capacity in std::fs::read #141211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 20, 2025

Conversation

fluiderson
Copy link
Contributor

This change restores the previous behavior prior to #117925. That PR was made to handle OOM errors that turn into a panic with Vec::with_capacity. try_reserve_exact was used for that since there was no try_with_capacity method at the time. It was added later in #120504. I think it'd a better fit here.

@rustbot
Copy link
Collaborator

rustbot commented May 18, 2025

r? @thomcc

rustbot has assigned @thomcc.
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

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels May 18, 2025
@thomcc
Copy link
Member

thomcc commented May 19, 2025

@bors r+

@bors
Copy link
Collaborator

bors commented May 19, 2025

📌 Commit 0dec3fe has been approved by thomcc

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels May 19, 2025
@bors
Copy link
Collaborator

bors commented May 20, 2025

⌛ Testing commit 0dec3fe with merge 22dca7e...

bors added a commit to rust-lang-ci/rust that referenced this pull request May 20, 2025
Replace `try_reserve_exact` with `try_with_capacity` in `std::fs::read`

This change restores the previous behavior prior to rust-lang#117925. That PR was made to handle OOM errors that turn into a panic with `Vec::with_capacity`. `try_reserve_exact` was used for that since there was no `try_with_capacity` method at the time. It was added later in rust-lang#120504. I think it'd a better fit here.
@Zalathar
Copy link
Contributor

@bors retry (bumping in favour of rollup that includes this PR)

bors added a commit to rust-lang-ci/rust that referenced this pull request May 20, 2025
Rollup of 5 pull requests

Successful merges:

 - rust-lang#141211 (Replace `try_reserve_exact` with `try_with_capacity` in `std::fs::read`)
 - rust-lang#141257 (trim cache module in utils bootstrap)
 - rust-lang#141259 (Update books)
 - rust-lang#141261 (current_dll_path: fix mistake in assertion message)
 - rust-lang#141262 (Properly remove Noratrieb from review rotation)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 66388d9 into rust-lang:master May 20, 2025
6 of 7 checks passed
@rustbot rustbot added this to the 1.89.0 milestone May 20, 2025
@bors
Copy link
Collaborator

bors commented May 20, 2025

⌛ Testing commit 0dec3fe with merge a8e4c68...

rust-timer added a commit to rust-lang-ci/rust that referenced this pull request May 20, 2025
Rollup merge of rust-lang#141211 - fluiderson:dev, r=thomcc

Replace `try_reserve_exact` with `try_with_capacity` in `std::fs::read`

This change restores the previous behavior prior to rust-lang#117925. That PR was made to handle OOM errors that turn into a panic with `Vec::with_capacity`. `try_reserve_exact` was used for that since there was no `try_with_capacity` method at the time. It was added later in rust-lang#120504. I think it'd a better fit here.
@fluiderson fluiderson deleted the dev branch May 20, 2025 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-libs Relevant to the library team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants