4 ms·
The blog post addresses this by using relative paths. Tested up to a path length of 30k apparently.
by Arch-TK 2y ago
The blog post addresses this by using relative paths. Tested up to a path length of 30k apparently.
- omoikane 2y agoI believe somewhere after 30k is when they will run into file system limits. Despite being able to create directories nested to arbitrary depth with short file names, find() might not be able to read a directory if the total path length is too long. I found this out when I couldn't open a file with the path "./././name.h" where there are lots of "./" in front. And the reason why I got so many "./" was due to a clang preprocessor bug that modifies __FILE__: https://github.com/llvm/llvm-project/issues/43825 https://github.com/llvm/llvm-project/issues/43825