Feature gate: `#![feature(core_io_borrowed_buf)]` This is a tracking issue for an MVP of `core::io`, which contains an OS-independent subset of `std::io`. ### Public API The initial API of this module consists of [`BorrowedBuf`](https://doc.rust-lang.org/std/io/struct.BorrowedBuf.html) and [`BorrowedCursor`](https://doc.rust-lang.org/std/io/struct.BorrowedCursor.html), which were previously only available in `std`. ### Steps / History - [x] https://github.com/rust-lang/rust/pull/97015 - [x] https://github.com/rust-lang/rust/pull/117694 - [ ] Final comment period (FCP)[^1] - [ ] Stabilization PR <!-- Once the feature has gone through a few release cycles and there are no unresolved questions left, the feature might be ready for stabilization. If this feature didn't go through the RFC process, a final comment period (FCP) is always needed before stabilization. This works as follows: A library API team member can kick off the stabilization process, at which point the rfcbot will ask all the team members to verify they agree with stabilization. Once enough members agree and there are no concerns, the final comment period begins: this issue will be marked as such and will be listed in the next This Week in Rust newsletter. If no blocking concerns are raised in that period of 10 days, a stabilization PR can be opened by anyone. --> ### Unresolved Questions <!-- Include any open questions that need to be answered before the feature can be stabilised. If multiple (unrelated) big questions come up, it can be a good idea to open a separate issue for each, to make it easier to keep track of the discussions. It's useful to link any relevant discussions and conclusions (whether on GitHub, Zulip, or the internals forum) here. --> - None yet. [^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html