Skip to content

Tracking Issue for #![feature(const_io_structs)] #78812

Closed

Description

@a1phyr

This is a tracking issue for #![feature(const_io_structs)]

New const functions are:

  • io::Cursor::new
  • io::Cursor::get_ref
  • io::Cursor::position
  • io::empty
  • io::repeat
  • io::sink

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

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Nov 6, 2020
  2. added a commit that references this issue on Nov 7, 2020
  3. added 4 commits that reference this issue on Nov 7, 2020
  4. added
    I-libs-radarLibs issues that are tracked on the team's radar.
    on Dec 16, 2020
  5. added
    A-ioArea: `std::io` (note: `std::fs`, `std::net`, `std::path` are A-filesystem, A-net, A-path)
    on Jan 6, 2021
  6. jhpratt commented on Apr 20, 2021

    @jhpratt
    Member

    Are there any blockers for these? They appear to all have straightforward implementations that should work on stable.

    CC @dtolnay who r+'d the original PR

  7. Stebalien commented on Aug 18, 2023

    @Stebalien
    Contributor

    Hey, I'd love to have this if we can make it stable. This would make it possible to, e.g., create "global" spooled temporary files without lazy_static:

    static BUFFER: Mutex<SpooledTempFile> = Mutex::new(tempfile::SpooledTempFile::new(1024 * 1024));
  8. rfcbot commented on Apr 5, 2024

    @rfcbot

    Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged team members:

    No concerns currently listed.

    Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

    See this document for info about what commands tagged team members can give me.

  9. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Apr 5, 2024
  10. 3 remaining items

  11. rfcbot commented on Apr 6, 2024

    @rfcbot

    🔔 This is now entering its final comment period, as per the review above. 🔔

  12. oli-obk commented on Apr 6, 2024

    @oli-obk
    Contributor

    All of these lgtm from a @rust-lang/wg-const-eval perspective. they are just trivial accessors or constructor funcions

  13. added
    to-announceAnnounce this issue on triage meeting
    and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Apr 16, 2024
  14. rfcbot commented on Apr 16, 2024

    @rfcbot

    The final comment period, with a disposition to merge, as per the review above, is now complete.

    As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

    This will be merged soon.

  15. added a commit that references this issue on Apr 17, 2024
  16. added a commit that references this issue on Apr 17, 2024
  17. added a commit that references this issue on Apr 17, 2024
  18. added a commit that references this issue on Apr 17, 2024
  19. added a commit that references this issue on Apr 17, 2024
  20. added
    A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)
    on Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-const-evalArea: Constant evaluation, covers all const contexts (static, const fn, ...)A-ioArea: `std::io` (note: `std::fs`, `std::net`, `std::path` are A-filesystem, A-net, A-path)C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCI-libs-radarLibs issues that are tracked on the team's radar.T-libs-api[DEPRECATED; DO NOT USE]disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions