Why does joining paths completely replace the original path in Rust?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I don't understand how Rust concatenates file paths. Why doesn't this work:
fn main() {
let root = std::path::Path::new("resources/");
let uri = std::path::Path::new("/js/main.js");
let path = root.join(uri);
assert_eq!(path.to_str(), Some("resources/js/main.js"));
}
fails with:
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `Some("/js/main.js")`,
right: `Some("resources/js/main.js")`', src/main.rs:5:5
I see in the docs that "pushing an absolute path replaces the existing path", but this seems like a terrible idea that will catch a lot of people.
In that case, how do I safely strip the absolute path, or make it relative?
rust filepath
add a comment |
I don't understand how Rust concatenates file paths. Why doesn't this work:
fn main() {
let root = std::path::Path::new("resources/");
let uri = std::path::Path::new("/js/main.js");
let path = root.join(uri);
assert_eq!(path.to_str(), Some("resources/js/main.js"));
}
fails with:
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `Some("/js/main.js")`,
right: `Some("resources/js/main.js")`', src/main.rs:5:5
I see in the docs that "pushing an absolute path replaces the existing path", but this seems like a terrible idea that will catch a lot of people.
In that case, how do I safely strip the absolute path, or make it relative?
rust filepath
1
I guess you can see this: github.com/rust-lang/rust/issues/16507 discussion
– Stoogy
Nov 22 '18 at 12:05
@Stoogy thanks; I've commented on the issue.
– Petrus Theron
Nov 22 '18 at 17:28
add a comment |
I don't understand how Rust concatenates file paths. Why doesn't this work:
fn main() {
let root = std::path::Path::new("resources/");
let uri = std::path::Path::new("/js/main.js");
let path = root.join(uri);
assert_eq!(path.to_str(), Some("resources/js/main.js"));
}
fails with:
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `Some("/js/main.js")`,
right: `Some("resources/js/main.js")`', src/main.rs:5:5
I see in the docs that "pushing an absolute path replaces the existing path", but this seems like a terrible idea that will catch a lot of people.
In that case, how do I safely strip the absolute path, or make it relative?
rust filepath
I don't understand how Rust concatenates file paths. Why doesn't this work:
fn main() {
let root = std::path::Path::new("resources/");
let uri = std::path::Path::new("/js/main.js");
let path = root.join(uri);
assert_eq!(path.to_str(), Some("resources/js/main.js"));
}
fails with:
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `Some("/js/main.js")`,
right: `Some("resources/js/main.js")`', src/main.rs:5:5
I see in the docs that "pushing an absolute path replaces the existing path", but this seems like a terrible idea that will catch a lot of people.
In that case, how do I safely strip the absolute path, or make it relative?
rust filepath
rust filepath
edited Nov 22 '18 at 21:24
Shepmaster
163k16337483
163k16337483
asked Nov 22 '18 at 11:50
Petrus TheronPetrus Theron
13.5k24114227
13.5k24114227
1
I guess you can see this: github.com/rust-lang/rust/issues/16507 discussion
– Stoogy
Nov 22 '18 at 12:05
@Stoogy thanks; I've commented on the issue.
– Petrus Theron
Nov 22 '18 at 17:28
add a comment |
1
I guess you can see this: github.com/rust-lang/rust/issues/16507 discussion
– Stoogy
Nov 22 '18 at 12:05
@Stoogy thanks; I've commented on the issue.
– Petrus Theron
Nov 22 '18 at 17:28
1
1
I guess you can see this: github.com/rust-lang/rust/issues/16507 discussion
– Stoogy
Nov 22 '18 at 12:05
I guess you can see this: github.com/rust-lang/rust/issues/16507 discussion
– Stoogy
Nov 22 '18 at 12:05
@Stoogy thanks; I've commented on the issue.
– Petrus Theron
Nov 22 '18 at 17:28
@Stoogy thanks; I've commented on the issue.
– Petrus Theron
Nov 22 '18 at 17:28
add a comment |
1 Answer
1
active
oldest
votes
This is because "/js/main.js"
is treated as an absolute path (doc)
If path is absolute, it replaces the current path.
On Windows:
- if
path
has a root but no prefix (e.g. windows), it replaces everything except for the prefix (if any) ofself
.
- if
path
has a prefix but no root, it replacesself
.
If you change your example to "js/main.js"
and then use join
, it will be properly constructed (playground)
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
FYI:os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.
– Matthieu M.
Nov 22 '18 at 12:08
1
@PetrusTheron I would suggest not using/
at all. You can omit them completly.
– hellow
Nov 22 '18 at 12:11
2
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
1
@PetrusTheron you can usePath::strip_prefix
to remove the leading/
: playground
– Jmb
Nov 22 '18 at 15:54
|
show 4 more comments
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430401%2fwhy-does-joining-paths-completely-replace-the-original-path-in-rust%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is because "/js/main.js"
is treated as an absolute path (doc)
If path is absolute, it replaces the current path.
On Windows:
- if
path
has a root but no prefix (e.g. windows), it replaces everything except for the prefix (if any) ofself
.
- if
path
has a prefix but no root, it replacesself
.
If you change your example to "js/main.js"
and then use join
, it will be properly constructed (playground)
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
FYI:os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.
– Matthieu M.
Nov 22 '18 at 12:08
1
@PetrusTheron I would suggest not using/
at all. You can omit them completly.
– hellow
Nov 22 '18 at 12:11
2
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
1
@PetrusTheron you can usePath::strip_prefix
to remove the leading/
: playground
– Jmb
Nov 22 '18 at 15:54
|
show 4 more comments
This is because "/js/main.js"
is treated as an absolute path (doc)
If path is absolute, it replaces the current path.
On Windows:
- if
path
has a root but no prefix (e.g. windows), it replaces everything except for the prefix (if any) ofself
.
- if
path
has a prefix but no root, it replacesself
.
If you change your example to "js/main.js"
and then use join
, it will be properly constructed (playground)
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
FYI:os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.
– Matthieu M.
Nov 22 '18 at 12:08
1
@PetrusTheron I would suggest not using/
at all. You can omit them completly.
– hellow
Nov 22 '18 at 12:11
2
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
1
@PetrusTheron you can usePath::strip_prefix
to remove the leading/
: playground
– Jmb
Nov 22 '18 at 15:54
|
show 4 more comments
This is because "/js/main.js"
is treated as an absolute path (doc)
If path is absolute, it replaces the current path.
On Windows:
- if
path
has a root but no prefix (e.g. windows), it replaces everything except for the prefix (if any) ofself
.
- if
path
has a prefix but no root, it replacesself
.
If you change your example to "js/main.js"
and then use join
, it will be properly constructed (playground)
This is because "/js/main.js"
is treated as an absolute path (doc)
If path is absolute, it replaces the current path.
On Windows:
- if
path
has a root but no prefix (e.g. windows), it replaces everything except for the prefix (if any) ofself
.
- if
path
has a prefix but no root, it replacesself
.
If you change your example to "js/main.js"
and then use join
, it will be properly constructed (playground)
edited Nov 22 '18 at 12:08
answered Nov 22 '18 at 12:06
hellowhellow
5,80252344
5,80252344
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
FYI:os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.
– Matthieu M.
Nov 22 '18 at 12:08
1
@PetrusTheron I would suggest not using/
at all. You can omit them completly.
– hellow
Nov 22 '18 at 12:11
2
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
1
@PetrusTheron you can usePath::strip_prefix
to remove the leading/
: playground
– Jmb
Nov 22 '18 at 15:54
|
show 4 more comments
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
FYI:os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.
– Matthieu M.
Nov 22 '18 at 12:08
1
@PetrusTheron I would suggest not using/
at all. You can omit them completly.
– hellow
Nov 22 '18 at 12:11
2
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
1
@PetrusTheron you can usePath::strip_prefix
to remove the leading/
: playground
– Jmb
Nov 22 '18 at 15:54
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
Thanks, then how do I treat the incoming path as always relative?
– Petrus Theron
Nov 22 '18 at 12:07
FYI:
os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.– Matthieu M.
Nov 22 '18 at 12:08
FYI:
os.path.join
has the same behavior in Python. I am not sure why, but at least there's some consistency there.– Matthieu M.
Nov 22 '18 at 12:08
1
1
@PetrusTheron I would suggest not using
/
at all. You can omit them completly.– hellow
Nov 22 '18 at 12:11
@PetrusTheron I would suggest not using
/
at all. You can omit them completly.– hellow
Nov 22 '18 at 12:11
2
2
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
@TimDiekmann quoting the doc: "The difference between absolutize and canonicalize methods is that absolutize does not care about whether the file exists and what the file really is." ;)
– hellow
Nov 22 '18 at 12:16
1
1
@PetrusTheron you can use
Path::strip_prefix
to remove the leading /
: playground– Jmb
Nov 22 '18 at 15:54
@PetrusTheron you can use
Path::strip_prefix
to remove the leading /
: playground– Jmb
Nov 22 '18 at 15:54
|
show 4 more comments
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53430401%2fwhy-does-joining-paths-completely-replace-the-original-path-in-rust%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
I guess you can see this: github.com/rust-lang/rust/issues/16507 discussion
– Stoogy
Nov 22 '18 at 12:05
@Stoogy thanks; I've commented on the issue.
– Petrus Theron
Nov 22 '18 at 17:28