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 Path/PathBuf normalization methods #47402

Closed
linclelinkpart5 opened this issue Jan 12, 2018 · 3 comments
Closed

Tracking issue for Path/PathBuf normalization methods #47402

linclelinkpart5 opened this issue Jan 12, 2018 · 3 comments
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. 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

@linclelinkpart5
Copy link

Tracking rust-lang/rfcs#2208

@sfackler sfackler added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. B-unstable Blocker: Implemented in the nightly compiler and unstable. labels Jan 12, 2018
@sfackler sfackler changed the title Path/PathBuf normalization methods Tracking issue for Path/PathBuf normalization methods Jan 12, 2018
@pietroalbini pietroalbini added the C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC label Feb 13, 2018
@akavel
Copy link
Contributor

akavel commented Jan 23, 2019

Umh, sorry, I'm not well versed in Rust RFCs: could you please help me understand how this issue is intended to work, given that the rust-lang/rfcs#2208 it tracks is "closed in favor of 47402 [i.e. this very tracking issue]"? The tracked issue is closed, because a tracking issue is open, but then it points back to the closed tracked issue? So, is this worked on? Is it not? What can I do if I wanted to, say, submit a solution?

@matklad
Copy link
Member

matklad commented Feb 13, 2019

@Mark-Simulacrum
Copy link
Member

Closing in favor of rust-lang/rfcs#2208, which is the more appropriate place to track this (since we don't have an implementation yet; see my comment there too: rust-lang/rfcs#2208 (comment)).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. 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

6 participants