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 os_string_pathbuf_leak #125965

Open
1 of 3 tasks
its-the-shrimp opened this issue Jun 4, 2024 · 1 comment
Open
1 of 3 tasks

Tracking Issue for os_string_pathbuf_leak #125965

its-the-shrimp opened this issue Jun 4, 2024 · 1 comment
Labels
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@its-the-shrimp
Copy link
Contributor

its-the-shrimp commented Jun 4, 2024

Feature gate: #![feature(os_string_pathbuf_leak)]

This is a tracking issue for rust-lang/libs-team#389

Public API

impl OsString {
    fn leak<'a>(self) -> &'a mut OsStr { ... }
}

impl PathBuf {
    fn leak<'a>(self) -> &'a mut Path { ... }
}

Steps / History

Unresolved Questions

  • None yet.

Footnotes

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

@its-the-shrimp its-the-shrimp added C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Jun 4, 2024
matthiaskrgr added a commit to matthiaskrgr/rust that referenced this issue Jun 5, 2024
…ak, r=workingjubilee

Implement `os_string_pathbuf_leak`

implementation of rust-lang#125965

ACP: rust-lang/libs-team#389 [ Accepted ]
bors added a commit to rust-lang-ci/rust that referenced this issue Jun 8, 2024
…, r=workingjubilee

Implement `os_string_pathbuf_leak`

implementation of rust-lang#125965

ACP: rust-lang/libs-team#389 [ Accepted ]
@its-the-shrimp
Copy link
Contributor Author

This feature is fairly small & uncontroversial, is it OK to proceed with the stabilisation PR at this point?

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 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

1 participant