Map EEXIST to PathAlreadyExists error, closes #20226 #20231
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created a patch for #20226, which maps
EEXIST
to thePathAlreadyExists
error on Unix. To test this, I usemkdir
, which raisesEEXIST
if the directory already exists.On Windows, I map
ERROR_ALREADY_EXISTS
toPathAlreadyExist
, but I am note sure ifmkdir
on Windows raisesERROR_ALREADY_EXISTS
and do not have a Windows installation handy for testing.And I noticed another thing. No error seems to map to
IoErrorKind::PathDoesntExist
and I am wondering what the difference toFileNotFound
is?