summaryrefslogtreecommitdiff
path: root/include/ruby/internal/intern
diff options
context:
space:
mode:
authorStan Lo <stan.lo@shopify.com>2024-04-02 21:41:40 +0100
committergit <svn-admin@ruby-lang.org>2024-04-12 13:55:35 +0000
commit0924ff2d390084922fbcebada20b968fa3e8238c (patch)
tree312413d4a145a8bac53ee358d34351225af61b65 /include/ruby/internal/intern
parentabd05c848f437405e10410ded2a3d666e1b9bba5 (diff)
[ruby/prism] Fix parser translation's heredoc whitespace calculation
Given this example: ```rb <<~HEREDOC #{x} HEREDOC ``` Both the parser gem and Prism's translation layer would generate the following AST: ``` s(:dstr, s(:begin, s(:int, 1)), s(:str, " a\n")) ``` However, the parser gem inserts a empty string node into this node's location, like: ``` <Parser::Source::Map::Heredoc:0x0000000104ce73b8 @expression=#<Parser::Source::Range (string) 0...10>, @heredoc_body=#<Parser::Source::Range (string) 11...20>, @heredoc_end=#<Parser::Source::Range (string) 20...27>, @node=s(:dstr, s(:str, ""), s(:begin, s(:int, 1)), s(:str, " a\n"))> ``` This is required to calculate the correct whitespace for the heredoc body. We need to adjust the translation layer to account for this. With this fix, we also won't need to ignore the tilde heredoc fixture anymore. https://github.com/ruby/prism/commit/e7372e3ba5
Diffstat (limited to 'include/ruby/internal/intern')
0 files changed, 0 insertions, 0 deletions