Skip to content

Tracking issue for the FromUtf8Error::as_bytes #40895

Description

@3Hren

Added in #40290 under the from_utf8_error_as_bytes feature flag.

Activity

  1. added
    B-unstableBlocker: Implemented in the nightly compiler and unstable.
    T-libs-api[DEPRECATED; DO NOT USE]
    on Mar 29, 2017
  2. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Jul 22, 2017
  3. Mark-Simulacrum commented on Jan 17, 2018

    @Mark-Simulacrum
    Member

    @rust-lang/libs Nominating for stabilization. Seems like a good addition with no (known) blockers.

  4. sfackler commented on Jan 18, 2018

    @sfackler
    Member

    @rfcbot fcp merge

  5. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Jan 18, 2018
  6. rfcbot commented on Jan 18, 2018

    @rfcbot

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

    No concerns currently listed.

    Once these reviewers reach consensus, 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.

  7. rfcbot commented on Jan 23, 2018

    @rfcbot

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

  8. added
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    and removed
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Jan 23, 2018
  9. rfcbot commented on Jan 23, 2018

    @rfcbot

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

  10. rfcbot commented on Jan 23, 2018

    @rfcbot

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

  11. rfcbot commented on Feb 2, 2018

    @rfcbot

    The final comment period is now complete.

  12. added a commit that references this issue on Mar 17, 2018
    b57ea56
  13. ErichDonGubler commented on Mar 19, 2018

    @ErichDonGubler
    Contributor

    How does one contribute after the FCP has gone through for stabilization? I'm not familiar with it and want to learn. :) Is that something the community contributes, or do we have a big stabilization PR like this one?

  14. SimonSapin commented on Mar 19, 2018

    @SimonSapin
    Contributor

    Both are possible. In this case I see that #49121 has already been submitted.

  15. added a commit that references this issue on Mar 23, 2018
    59b5887
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

    B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE]final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions