Skip to content

Tracking Issue for LocalKey<Cell>::update #143989

Closed

Description

@camsteffen

Feature gate: #![feature(local_key_cell_update)]

This is a tracking issue for adding LocalKey::<Cell<T>>::update, similar to other LocalKey::<Cell<T>> methods.

ACP: rust-lang/libs-team#617

Public API

impl<T: 'static> LocalKey<Cell<T>> {
    pub fn update(&'static self, f: impl FnOnce(T) -> T) where T: Copy;
}

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

Activity

  1. added
    T-libs-api[DEPRECATED; DO NOT USE]
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Jul 15, 2025
  2. added 2 commits that reference this issue on Jul 16, 2025
  3. added a commit that references this issue on Jul 16, 2025
  4. added a commit that references this issue on Jul 21, 2025
  5. added a commit that references this issue on Jul 29, 2025
  6. pthariensflame commented on Jan 19, 2026

    @pthariensflame
    Contributor

    Is this ready to be stabilized? We don't see any outstanding concerns, or indeed any questions about this API’s shape or behavior.

  7. tgross35 commented on Jun 11, 2026

    @tgross35
    Member

    Stabilization PR #157734

  8. linked a pull request that will close this issueStabilize `local_key_cell_update` #157734on Jun 11, 2026
  9. Amanieu commented on Jun 16, 2026

    @Amanieu
    Member

    @rfcbot merge libs-api

  10. rust-rfcbot commented on Jun 16, 2026

    @rust-rfcbot
    Collaborator

    @Amanieu 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.

  11. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
    on Jun 16, 2026
  12. 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 Jun 25, 2026
  13. rust-rfcbot commented on Jun 25, 2026

    @rust-rfcbot
    Collaborator

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

  14. added and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Jul 5, 2026
  15. rust-rfcbot commented on Jul 5, 2026

    @rust-rfcbot
    Collaborator

    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.

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

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-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