Fix LWG-3699 lexically_relative on UNC drive paths (\\?\C:\...) results in a default-constructed value#2867
Conversation
|
Marking |
StephanTLavavej
left a comment
There was a problem hiding this comment.
Looks good to me - all I noticed were very minor issues/questions.
|
@StephanTLavavej fixed :) |
|
We talked about this at the weekly maintainer meeting and decided that the strategy of "UNC paths can be lexically relative to one another, but not UNC and DOS" is reasonable given the Standard's wording and our behavior here (where we consider |
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
|
Thanks for improving filesystem behavior on Windows! 🗄️ 🗂️ 💾 |
…esults in a default-constructed value (microsoft#2867) Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
The output: The “root name” component extracted from the path is reported as an empty string ( The root directory output is |
Fixes #2256 and LWG-3699
This is one choice of how to implement this; it makes
lexically_relativetreat\\?\<drive letter>:\as equivalent to<drive letter>:\; another option would just be to allow\\?\<drive letter>:\and not have them be equivalent.