rust-lang / rust-lang/rust

Tracking Issue for const `Cell` methods that depend on const traits

Open
#147,787 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-unimplemented T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(const_cell_traits)]

This is a tracking issue for const Cell methods that depend on const traits.

Public API
impl<T> Cell<T> {
    pub const fn set(&self, val: T) where T: [const] Destruct;
    
    // NOTE: Copy should imply const Destruct, but it doesn't atm
    pub const fn update(&self, f: impl [const] FnOnce(T) -> T) where T: Copy + [const] Destruct;

    pub const fn take(&self) -> T where T: [const] Default;
}
Steps / History

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

  • Implementation: #147788
  • Final comment period (FCP)^1
  • Stabilization PR
Unresolved Questions
  • None yet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the public API and the implementation issue #147788, which is listed as the first step in this tracking issue. The feature gate is const_cell_traits, and the tracked work is complete only when implementation, the final comment period, and a stabilization PR have been addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.