Tracking issue for Path/PathBuf normalization methods #47402

Activity

1. sfackler

   added

   T-libs-api[DEPRECATED; DO NOT USE][DEPRECATED; DO NOT USE]

   B-unstableBlocker: Implemented in the nightly compiler and unstable.Blocker: Implemented in the nightly compiler and unstable.

   on Jan 12, 2018
2. sfackler

   changed the title [-]Path/PathBuf normalization methods[/-] [+]Tracking issue for Path/PathBuf normalization methods[/+] on Jan 12, 2018
3. emilyalbini

   added

   C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFC

   on Feb 13, 2018
4. akavel commented on Jan 23, 2019

   

   akavel

   on Jan 23, 2019

   Last edited by akavel

   Contributor

   More actions

   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?

   👍React with 👍1Reacted by Marco Farrugia
5. matklad commented on Feb 13, 2019

   

   matklad

   on Feb 13, 2019

   Contributor

   More actions

   for the reference, here's what Cargo uses:

   https://github.com/rust-lang/cargo/blob/2e4cfc2b7d43328b207879228a2ca7d427d188bb/src/cargo/util/paths.rs#L65-L90
6. Mark-Simulacrum commented on Mar 12, 2019

   

   Mark-Simulacrum

   on Mar 12, 2019

   Member

   More actions

   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)).
7. Mark-Simulacrum

   closed this as completedon Mar 12, 2019