2 ms·
There's two separate issues in play here: The first is the distinction between "owned" (i.e., heap-allocated) and "borrowed" (types). Arguably, there could hav
by jcranmer 6y ago
There's two separate issues in play here:
The first is the distinction between "owned" (i.e., heap-allocated) and "borrowed" (types). Arguably, there could have been better language support for this to fix this issue.
The second is the fact that the underlying OS rules for strings and paths do not conform to any sane string requirements on most systems. If you collapse this into normal strings, then you end up with situations where you can't interact with your OS properly.