I will take back the long path issue though. It seems this application only uses the current directory, which (at least currently) can never be long.
18.11.2025 17:39
👍 1
🔁 0
💬 1
📌 0
I will take back the long path issue though. It seems this application only uses the current directory, which (at least currently) can never be long.
I was specifically replying in regards to Windows where argv is allocated by the CRT by parsing the command line. The command line is in UTF-16 so it also converts it to a "multibyte" code page. This conversion is potentially lossy
It will (probably) work but it's not zero allocation and it introduced a few issues (text encoding and long path handling).
Interesting but I mean editions are tied to crates so it couldn't literally be part of an edition.
An opt-in field in rust-toolchain could work. But that still means that users downloading thing from the internet may get random installs. Maybe we could make a distinction between CI and end users.
how would that be done?