Tweak nonewlines regex rewriting (#211) #212
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
Using \n+ in a regex doesn't make any sense for Sublime Text syntaxes, but let's not produce an invalid regex in that case.
keith-hall
reviewed
Oct 4, 2018
src/parsing/yaml_load.rs
Outdated
| // Replacing `\n` with `$` in `\n?` or `\n+` would make parsing later fail | ||
| // with "target of repeat operator is invalid" | ||
| let c3 = self.peek(); | ||
| if c2 == b'n' && c3 != Some(b'?') && c3 != Some(b'+') { |
There was a problem hiding this comment.
I think it would make sense to also check for * here, as \n* -> $* would also be invalid
keith-hall
approved these changes
Oct 4, 2018
trishume
approved these changes
Oct 5, 2018
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.
Using
\n+in a regex doesn't make any sense for Sublime Text syntaxes, but let's not produce an invalid regex in that case.