4

Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_maybe_uninit_...

1 year ago

source link: https://github.com/rust-lang/rust/issues/75251
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

neoserver,ios ssh client

Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_maybe_uninit_as_ptr) #75251

1 of 3 tasks

RalfJung opened this issue Aug 7, 2020 · 9 comments

Comments

Member

RalfJung commented Aug 7, 2020 •

edited

This is a tracking issue for const MaybeUninit::as(_mut)_ptr.
The feature gate for the issue is #![feature(const_maybe_uninit_as_ptr)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses 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

Unresolved Questions

Implementation history

Added in make MaybeUninit::as_(mut_)ptr const #75250

DianaNites reacted with rocket emoji

added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label

changed the title ~~Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: maybe_uninit_const_as_ptr)~~

Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_)

changed the title ~~Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_)~~

Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_maybe_uninit_const_as_ptr)

changed the title ~~Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_maybe_uninit_const_as_ptr)~~

Tracking Issue for const MaybeUninit::as(_mut)_ptr (feature: const_maybe_uninit_as_ptr)

Member

jhpratt commented Oct 19, 2021

There doesn't appear to be any blockers for the non-mut version, unless I'm missing something?

Member

pnkfelix commented Sep 23, 2022

Visiting for T-compiler backlog bonanza. This seems likely to be ready to stabilize, but since I'm not certain, I'm tagging with "needs summary"

Also, we think the question of whether to stabilize these methods falls under T-libs domain, so tagging with that team label

@rustbot label: +T-libs +S-tracking-needs-summary

added S-tracking-needs-summary It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-libs Relevant to the library team, which will review and decide on the PR/issue.

labels

added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label

removed the T-libs Relevant to the library team, which will review and decide on the PR/issue. label

Member

pnkfelix commented Sep 23, 2022

(@m-ou-se pointed out that this is a libs-api team issue, not a libs implementation issue.)

Member

m-ou-se commented Sep 23, 2022

RalfJung and oli-obk reacted with thumbs up emoji

rfcbot commented Sep 23, 2022 •

edited by BurntSushi

Team member @m-ou-se 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.

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

Member

Author

RalfJung commented Sep 23, 2022

Cc @rust-lang/wg-const-eval but this should be uncontroversial

Member

fee1-dead commented Sep 23, 2022

No concerns with this.

Member

dtolnay commented Dec 20, 2022

I'm marking @yaahc's box because she has stepped down from T-libs-api after the point that this feature got proposed for FCP.

added the final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. label

rfcbot commented Dec 20, 2022

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

removed the proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Assignees

No one assigned

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. final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. S-tracking-needs-summary It's hard to tell what's been done and what hasn't! Someone should do some investigation. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Projects

None yet

Milestone

No milestone

Development

No branches or pull requests

8 participants

Recommend

About Joyk

Aggregate valuable and interesting links.
Joyk means Joy of geeK