Fix parsing of "\\\n" escaped sequences in various literals. #539
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.
Closes #537
Introduced
Literal#supports_line_continuation_via_slash?
method that returnstrue/false
depending on the type of the literal. I wasn't able to find any correlation between interpolation and escaping rules. Looks like that's a completely new separate property of the literal. Ruby ❤️Added spec that verifies that
"\\\n"
gets properly escaped for all kinds of literals. @whitequark Please let me know if I should convert it from acceptance table to a list of plain assertions.test data
ruby -e
bin/ruby-parse