Uh oh!
There was an error while loading. Please reload this page.
Implement FromStr for PathBuf - #48292
Conversation
rust-highfive
commented
Feb 17, 2018
r? @kennytm (rust_highfive has picked a reviewer for you, use r? to override) |
74984b3 to
5cfbda9Comparetopecongiro
commented
Feb 17, 2018
Implementing |
kennytm
commented
Feb 17, 2018
@topecongiro try to implement it for |
topecongiro
commented
Feb 17, 2018
@kennytm Thank you for the review! I added a commit to implement |
kennytm
commented
Feb 17, 2018
@topecongiro Oh sorry, looks like it is not possible to implement cc @rust-lang/libs — This PR introduces |
There was a problem hiding this comment.
Since parsing a Path will never fail, please make it an empty enum:
pubenumParsePathError{}Alternatively, simply return std::string::ParseError.
There was a problem hiding this comment.
We shouldn't reuse an existing type.
There was a problem hiding this comment.
The feature should not be rust1. Please create a feature name e.g. path_from_str and set the since to be 1.26.0.
f6c289c to
a9b935fCompareThere was a problem hiding this comment.
This should just be match *self {}.
alexcrichton
commented
Feb 26, 2018
kennytm
commented
Feb 26, 2018
Yeah following the implementation of (cc @topecongiro) |
shepmaster
commented
Mar 2, 2018
Ping from triage, @topecongiro ! Will you have time soon to address the feedback above? |
a9b935f to
05a9accComparetopecongiro
commented
Mar 5, 2018
I am sorry for the late response. I have updated the PR to use |
alexcrichton
commented
Mar 5, 2018
@rfcbot fcp merge |
Team member @alexcrichton has proposed to merge this. The next step is review by the rest of the tagged teams: Concerns:
Once a majority of reviewers approve (and none object), 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. |
dtolnay
commented
Mar 8, 2018
|
sfackler
commented
Mar 8, 2018
Both ParsePathError and string::ParseError are going to turn into typedefs for |
rfcbot
commented
Mar 8, 2018
🔔 This is now entering its final comment period, as per the review above. 🔔 |
sfackler
commented
Mar 8, 2018
My point was that we may not have to stabilize |
alexcrichton
commented
Mar 8, 2018
@bors: r+ |
bors
commented
Mar 8, 2018
📌 Commit 05a9acc has been approved by |
bors
commented
Mar 8, 2018
⌛ Testing commit 05a9acc with merge 38c616009116c7e770eb16020c6beba55dd46403... |
bors
commented
Mar 8, 2018
💔 Test failed - status-appveyor |
@bors retry rollup 3 hour timeout in It took 43 minutes to compile stage1-rustc 🙄. Timing breakdownRelevant logsFor comparison, the build timings of the all jobs in this build: Details
|
…athbuf, r=alexcrichton Implement FromStr for PathBuf Closesrust-lang#44431.
…r=sfackler Revert "Implement FromStr for PathBuf" This reverts commit 05a9acc. The libs team was discussing rust-lang#44431 today and the changes originally added in rust-lang#48292 and the conclusion was that we'd like to revert this for now until `!` is stable. This'll provide us maximal flexibility to tweak the error type here in the future, and it looks like `!` is close-ish to stabilization so hopefully this won't be delayed for too long.
Initially landed in rust-lang#48292 and reverted in rust-lang#50401. This time, use `std::string::ParseError` as suggested in rust-lang#44431 (comment)
Implement FromStr for PathBuf Initially landed in rust-lang#48292 and reverted in rust-lang#50401. This time, use `std::string::ParseError` as suggested in rust-lang#44431 (comment)
Implement FromStr for PathBuf Initially landed in rust-lang#48292 and reverted in rust-lang#50401. This time, use `std::string::ParseError` as suggested in rust-lang#44431 (comment)
Initially landed in rust-lang#48292 and reverted in rust-lang#50401. This time, use `std::string::ParseError` as suggested in rust-lang#44431 (comment)
Closes#44431.