Stop compiler from assuming UTF-8 encoding in strings #27
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A while back I had an issue with getting strings with non-ASCII characters in my code to work (I wanted this for better visibility in my code) and realized it was because the compiler was assuming I wanted UTF-8 encoding in my program. Normally this acts perfectly fine, but in my case (where I was using special non-ASCII characters) this lead to mojibake appearing instead of box drawing characters. I felt that adding this flag to the compiler would make it easier to fully use the console. I do see that this might cause similar problems on any library that wants UTF-8 in their strings though.