This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
Decode error message strings on windows #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is useful for issues like openethereum/parity-ethereum#6959. |
andresilva
force-pushed
the
fix-windows-error-messages
branch
from
8b32f32
to
37d93df
Compare
kirushik
approved these changes
Jan 11, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Use
local-encodingtrait to parse error messages, which on windows is done withMultiByteToWideChar. I haven't tested this but we're already using this crate for handling path strings on windows.