Consistent support for Windows-style filesystem paths (backslash separators) #6
Description
Right now, if we give a Windows-style path using backslashes \, the parsing seems to succeed w/o error.
However, the normalization process converts the backslash separated paths into Unix-style paths with forward slashes /. I'm not sure how much of this is influenced by me working in Linux/MacOS.
It makes sense that if you give a Windows-style path, you should return a Windows-style path in the parse output.