Skip to content

Tracking Issue for RFC 2930 (read-buf) #78485

Open

Description

@nikomatsakis

View all comments

This is a tracking issue for the RFC "2930" (rust-lang/rfcs#2930).
The feature gate for the issue is #![feature(read_buf)].

This is now called BorrowedBuf rather than ReadBuf.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved Questions

Implementation history

Activity

  1. added
    B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.
    T-libs-api[DEPRECATED; DO NOT USE]
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Oct 28, 2020
  2. nikomatsakis commented on Oct 28, 2020

    @nikomatsakis
    ContributorAuthor

    ( cc @rust-lang/libs )

  3. beepster4096 commented on Oct 28, 2020

    @beepster4096
    Contributor

    I'm interested in working on this.

    @rustbot claim

  4. added
    I-libs-radarLibs issues that are tracked on the team's radar.
    on Nov 6, 2020
  5. beepster4096 commented on Nov 8, 2020

    @beepster4096
    Contributor

    I am slightly confused by the API of ReadBufs. What return type should methods like initialized have: &[u8] or &[IoSlice]? If its the former, how do you know which slices are initialized/filled? If it's the latter, what happens if a slice is partially initialized/filled?

    edit: probably I should ask this on zulip instead of github

  6. sfackler commented on Nov 8, 2020

    @sfackler
    Member

    It would return &[IoSliceMut], and only include the slices that are fully initialized.

  7. programmerjake commented on Nov 8, 2020

    @programmerjake
    Member

    It would return &[IoSliceMut], and only include the slices that are fully initialized.

    I would have expected it to return (&[IoSliceMut], &[u8]) where it is some number of fully initialized buffers and the initialized portion of the partially initialized buffer.

  8. sfackler commented on Nov 8, 2020

    @sfackler
    Member

    Sure, that makes sense.

  9. added
    A-ioArea: `std::io`, `std::fs`, `std::net` and `std::path`
    on Nov 28, 2020
  10. sfackler commented on Dec 5, 2020

    @sfackler
    Member

    @drmeepster are you still working on this?

  11. beepster4096 commented on Dec 5, 2020

    @beepster4096
    Contributor

    Yeah, I am. Although I'm currently working on #79607 because I needed it for this.

  12. beepster4096 commented on Dec 17, 2020

    @beepster4096
    Contributor

    Okay, I can continue working on this now that we have MaybeUninit::write_slice

  13. 101 remaining items

  14. added a commit that references this issue on Apr 15, 2026
  15. added a commit that references this issue on Apr 15, 2026
  16. tgross35 commented on Aug 2, 2026

    @tgross35
    Member

    FCP has started on this at #117693 (comment)

  17. added 2 commits that reference this issue on Aug 4, 2026
  18. added a commit that references this issue on Aug 4, 2026
  19. added a commit that references this issue on Aug 4, 2026
  20. added
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    and removed
    T-libs-api[DEPRECATED; DO NOT USE]
    on Aug 12, 2026
  21. removed
    I-libs-radarLibs issues that are tracked on the team's radar.
    on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

A-ioArea: `std::io`, `std::fs`, `std::net` and `std::path`B-RFC-approvedBlocker: Approved by a merged RFC but not yet implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libsRelevant to the library team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions