Revert too-long char literal match changes #40
Merged
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
mcous
added a commit
that referenced
this pull request
Jan 25, 2016
Revert too-long char literal match changes
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.
This PR reverts the changes to the invalid character length matchers I introduced in #37. Turns out they broke highlighting for two character literals used on the same line (see #39). Oops.
Reverting that change means that
val tooLong = ''''will not be highlighted properly as an error, but I can't find an elegant way to do it. It might need its own matcher, and from playing around, that matcher will probably need to deal with escaped single-quotes as well. I'd like to release this first while I think about it / experiment.