Skip to content

Tracking Issue for const {OsString, PathBuf}::new #141520

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

Open
1 of 3 tasks
cyrgani opened this issue May 24, 2025 · 2 comments
Open
1 of 3 tasks

Tracking Issue for const {OsString, PathBuf}::new #141520

cyrgani opened this issue May 24, 2025 · 2 comments
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC 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. S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@cyrgani
Copy link
Contributor

cyrgani commented May 24, 2025

Feature gate: #![feature(const_pathbuf_osstring_new)]

This is a tracking issue for making OsString::new and PathBuf::new const functions.

Public API

impl OsString {
    pub const fn new() -> OsString;
}
impl PathBuf {
    pub const fn new() -> PathBuf;
}

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

@cyrgani cyrgani added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC S-tracking-unimplemented Status: The feature has not been implemented. labels May 24, 2025
@Amanieu
Copy link
Member

Amanieu commented Jun 3, 2025

@rfcbot merge

@rfcbot
Copy link
Collaborator

rfcbot commented Jun 3, 2025

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

@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 Jun 3, 2025
@cyrgani cyrgani added S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR and removed S-tracking-unimplemented Status: The feature has not been implemented. labels Jun 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC 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. S-tracking-ready-to-stabilize Status: This is ready to stabilize; it may need a stabilization report and a PR 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

3 participants