Handle files with BOM in lexer.#285
Merged
SpaceManiac merged 3 commits intoSpaceManiac:masterfrom Sep 18, 2021
Merged
Conversation
Not sure if this is the best way to go about it, but it seems to work.
Cyberboss
approved these changes
Sep 17, 2021
SpaceManiac
requested changes
Sep 18, 2021
Owner
SpaceManiac
left a comment
There was a problem hiding this comment.
BOMs are terrible and I dislike that VS still uses them
Still a memmove but better than a full realloc.
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
3 participants
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.
This came up in OpenDream (blame VS...). Figured it wouldn't be too hard to fix here.
Not sure if this is the best way to go about it, but it seems to work.