Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Tracking Issue for core_io_borrowed_buf #117693

Open
1 of 3 tasks
jmillikin opened this issue Nov 8, 2023 · 2 comments
Open
1 of 3 tasks

Tracking Issue for core_io_borrowed_buf #117693

jmillikin opened this issue Nov 8, 2023 · 2 comments
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@jmillikin
Copy link
Contributor

jmillikin commented Nov 8, 2023 •
edited

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 and BorrowedCursor, which were previously only available in std.

Steps / History

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
@jmillikin jmillikin added C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Nov 8, 2023
This was referenced Nov 8, 2023
Merged
Closed
@jmillikin jmillikin changed the title Tracking Issue for core::io Tracking Issue for core_io_borrowed_buf Nov 8, 2023
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this issue Nov 8, 2023
@GuillaumeGomez
Rollup merge of rust-lang#117694 - jmillikin:core-io-borrowed-buf, r=…
2627f72 
…m-ou-se

Move `BorrowedBuf` and `BorrowedCursor` from `std:io` to `core::io`

Tracking issue: rust-lang#117693

ACP: rust-lang/libs-team#290
TaKO8Ki added a commit to TaKO8Ki/rust that referenced this issue Nov 9, 2023
@TaKO8Ki
Rollup merge of rust-lang#117694 - jmillikin:core-io-borrowed-buf, r=…
58aa686 
…m-ou-se

Move `BorrowedBuf` and `BorrowedCursor` from `std:io` to `core::io`

Tracking issue: rust-lang#117693

ACP: rust-lang/libs-team#290
TaKO8Ki added a commit to TaKO8Ki/rust that referenced this issue Nov 9, 2023
@TaKO8Ki
Rollup merge of rust-lang#117694 - jmillikin:core-io-borrowed-buf, r=…
b4fa5b7 
…m-ou-se

Move `BorrowedBuf` and `BorrowedCursor` from `std:io` to `core::io`

Tracking issue: rust-lang#117693

ACP: rust-lang/libs-team#290
rust-timer added a commit to rust-lang-ci/rust that referenced this issue Nov 9, 2023
@rust-timer
Unrolled build for rust-lang#117694
7e928ee 
Rollup merge of rust-lang#117694 - jmillikin:core-io-borrowed-buf, r=m-ou-se

Move `BorrowedBuf` and `BorrowedCursor` from `std:io` to `core::io`

Tracking issue: rust-lang#117693

ACP: rust-lang/libs-team#290
@ctz ctz mentioned this issue Nov 10, 2023
Merged
cpu added a commit to cpu/rustls-ffi that referenced this issue Nov 15, 2023
@cpu
opt in to core_io_borrowed_buf
4f9ecfd 
Unbreaks builds using the read_buf feature.
Tracking issue: rust-lang/rust#117693
@cpu cpu mentioned this issue Nov 15, 2023
Merged
@tgross35 tgross35 mentioned this issue Feb 26, 2024
Open
5 tasks
@tgross35
Copy link
Contributor

tgross35 commented Feb 26, 2024 •
edited

These types in core could use a core::fmt::Write impl, but I am not sure how this is possible without conflicting with the blanket impl for std::io::Write.

@kyleholohan kyleholohan mentioned this issue Mar 6, 2024
Open
@taralx
Copy link
Contributor

taralx commented Mar 16, 2024

Is the intent to stabilize this at the same time as #78485 or independently of it?

@a1phyr a1phyr mentioned this issue Apr 8, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jmillikin @taralx @tgross35