Block string literals #126
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
- Adds no-newline character escape. - Marks unknown escape sequences as invalid. - Block string literals not yet used, requires restructuring of syntax.
- Include block containers w/ bugfixes - Add init tag handling to expressions
|
@Tronic these changes incorrect handle case with |
|
@kosz78 Did you get those cases fixed or should I look into that over the weekend? |
|
Could you please fix it? |
kosz78
added a commit
that referenced
this pull request
Mar 12, 2020
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.
Implements highlight for string block literals as discussed in nim-lang/RFCs#161
Additionally highlights any unknown string escapes. Otherwise should not affect existing code.