Rust Programming

8134 readers

1 users here now

founded 5 years ago

MODERATORS

nutomic@lemmy.ml

Joe@lemmy.ml

Announcing Rust 1.79.0 | Rust Blog (blog.rust-lang.org)

submitted 4 months ago by tmpod@lemmy.pt to c/rust@lemmy.ml

6 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ssokolow@lemmy.ml 0 points 4 months ago* (last edited 4 months ago) (1 children)

It still returns relative paths if the input was relative

False

and it doesn’t resolve “…”

I'll assume you meant .., since ... is an ordinary filename. (Aside from the "who remembers ...?" feature introduced in Windows 95's COMMAND.COM where cd ... was shorthand for doing cd .. twice and you could omit the space after cd if your target was all dots.)

The reason it doesn't do that is that, when symlinks get involved, /foo/bar/.. does not necessarily resolve to /foo and making that assumption could introduce a lurking security vulnerability in programs which use it.

[–] Killing_Spark@feddit.de 0 points 4 months ago* (last edited 4 months ago) (1 children)

Hm it seems I misread the documentation there. I know why it doesn't resolve the ".." and that's fine, it just seemed very unnecessary in combination with my flawed understanding of the relative path handling.

Edit: and just to be snarky: I didn't type "..." I typed "..". ;)

[–] ssokolow@lemmy.ml 0 points 4 months ago (1 children)

Edit: and just to be snarky: I didn’t type “…” I typed “…”. ;)

*chuckle* I think Lemmy typed those for you, because I typed three periods and got a Unicode ellipsis, and both of those are also unicode ellipses.

[–] Killing_Spark@feddit.de 0 points 4 months ago

Huh that might actually be an issue with your client, mine renders those as two dots