Stan Lo 0924ff2d39 [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. e7372e3ba5		2024-04-12 13:55:35 +00:00
..
compiler.rb	[ruby/prism] Fix parser translation's heredoc whitespace calculation	2024-04-12 13:55:35 +00:00
lexer.rb	[ruby/prism] Fix token incompatibility for Prism::Translation::Parser::Lexer	2024-03-16 17:55:38 +00:00
rubocop.rb	[ruby/prism] Use require_relative in the Prism codebase	2024-03-18 16:12:49 +00:00