Move std::io::Write to core::io#158541
Conversation
|
r? @Darksonn rustbot has assigned @Darksonn. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
@rustbot blocked |
22e4295 to
802f7d5
Compare
ec21a69 to
c806329
Compare
This comment has been minimized.
This comment has been minimized.
c806329 to
a4969f5
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
a4969f5 to
9dc5fd5
Compare
|
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. |
|
@rustbot ready |
|
r? clarfonthey |
Co-Authored-By: Clar Fon <[email protected]>
|
Few remaining comments, otherwise looks good.
|
Co-Authored-By: Clar Fon <[email protected]>
Moves unsafe code from `alloc::io` into `alloc::vec`. A more general `try_extend_from_slice` may be useful in the future, but that requires changing how specialization is done for `SpecExtend` and that's a lot for an internal-only function.
|
@bors r+ rollup=iffy Relatively large |
…rfonthey Move `std::io::Write` to `core::io` ACP: rust-lang/libs-team#755 Tracking issue: rust-lang#154046 Split From: rust-lang#156527 ~~Blocked On: rust-lang#158537 ~~Blocked On: rust-lang#158540 ## Description Moves `std::io::Write` to `core::io`. This is effectively a direct cut and paste, but with a large diff due to how many implementations need to be moved into `alloc` and `core`. Blocked on rust-lang#158537 and rust-lang#158540. --- ## Notes * No AI tooling of any kind was used during the creation of this PR. * Please see rust-lang#154046 (comment) for a review order and broader context for this PR.
View all comments
ACP: rust-lang/libs-team#755
Tracking issue: #154046
Split From: #156527
Blocked On: #158537Blocked On: #158540Description
Moves
std::io::Writetocore::io. This is effectively a direct cut and paste, but with a large diff due to how many implementations need to be moved intoallocandcore. Blocked on #158537 and #158540.Notes
alloc::ioandcore::io#154046 (comment) for a review order and broader context for this PR.