Announcing Rust 1.79.0 | Rust Blog
Announcing Rust 1.79.0 | Rust Blog
https://blog.rust-lang.org/2024/06/13/Rust-1.79.0.html
Empowering everyone to build reliable and efficient software.
https://blog.rust-lang.org/2024/06/13/Rust-1.79.0.html
Empowering everyone to build reliable and efficient software.
It still returns relative paths if the input was relative
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.
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 "..". ;)
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.
I'm using the web UI, so I'm assuming whatever broad-spectrum Markdown rendering library it uses has smart quote rendering turned on.