Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Issue for #![feature(const_unsafecell_get_mut)] #88836

Open
1 of 3 tasks
WaffleLapkin opened this issue Sep 10, 2021 · 6 comments
Open
1 of 3 tasks

Tracking Issue for #![feature(const_unsafecell_get_mut)] #88836

WaffleLapkin opened this issue Sep 10, 2021 · 6 comments
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@WaffleLapkin
Copy link
Member

Feature gate: #![feature(const_unsafecell_get_mut)]

This is a tracking issue for UnsafeCell::get_mut as a const fn.

Public API

// core::cell

impl<T> UnsafeCell<T> {
    pub const fn get_mut(&mut self) -> &mut T;
}

Steps / History

Unresolved Questions

  • None yet.
@WaffleLapkin WaffleLapkin added C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Sep 10, 2021
@RalfJung
Copy link
Member

Cc @rust-lang/wg-const-eval

@tgross35
Copy link
Contributor

This is blocked on #57349, correct?

@RalfJung
Copy link
Member

Yeah, pretty much all the mutable reference/pointer stuff in const is blocked on that.

@workingjubilee workingjubilee added the I-libs-api-nominated Nominated for discussion during a libs-api team meeting. label Sep 19, 2024
@workingjubilee
Copy link
Member

etc. etc. #57349 landed now let's see if we have consensus for stabilizing this?

@dtolnay
Copy link
Member

dtolnay commented Sep 19, 2024

@rfcbot
Copy link

rfcbot commented Sep 19, 2024

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.

@rfcbot rfcbot added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. labels Sep 19, 2024
@dtolnay dtolnay removed the I-libs-api-nominated Nominated for discussion during a libs-api team meeting. label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

6 participants