13 ms·
The problem with using strict UTF-8 for paths is that paths aren't guaranteed to be valid UTF-8. How do you want to write a program that opens a path who's name
by adgjlsfhk1 4y ago
The problem with using strict UTF-8 for paths is that paths aren't guaranteed to be valid UTF-8. How do you want to write a program that opens a path who's name is invalid UTF-8?
- masklinn 4y ago> The problem with using strict UTF-8 for paths is that paths aren't guaranteed to be valid UTF-8. Ok but I’m not saying to do that. I’m saying if you have not-utf8 strings don’t call them UTF8. > How do you want to write a program that opens a path who's name is invalid UTF-8? That’s not my problem given I’m not advocating for that.
- StefanKarpinski 4y agoThe issue is that when you're implementing something like a programming language or a robust general purpose utility, then simply not being able to open—or list or remove or stat—paths with invalid names is not really acceptable.
- masklinn 4y agoDo you actually read comments before replying?