You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be pretty nice to have normalization (see #1) enforced automatically by an abstract datatype. That way you could take any path, convert it to an equivalent VerbatimPath, and know for sure you'd get all the usual conveniences without running into 260-character path-length restrictions.
Users would still need to understand that the path's string representation was a verbatim path, e.g. for serializing or passing to OS API's.
The text was updated successfully, but these errors were encountered:
I was literally just musing about this exact thing. It would be great to have a type to enforce this. AFAIK it's safe to pass these paths to all Windows APIs, so it should be OK to use them liberally and have the type implement Deref<Path> and AsRef<Path>.
It'd be pretty nice to have normalization (see #1) enforced automatically by an abstract datatype. That way you could take any path, convert it to an equivalent
VerbatimPath
, and know for sure you'd get all the usual conveniences without running into 260-character path-length restrictions.Users would still need to understand that the path's string representation was a verbatim path, e.g. for serializing or passing to OS API's.
The text was updated successfully, but these errors were encountered: