> It makes no sense for the range of the syntactic block here to include the entire expression of the call and its arguments. If I'm understanding you correctly, then what you would like for source_range for the example for `foo` and ...kddnewton (Kevin Newton)
Necessarily if the ABI changes, it means the AST shape changed. So how can you possibly expect it to work "whether the loaded prism gem ABI matches that or not". If the AST shape changed, then you're guessing. Unless you're once again su...kddnewton (Kevin Newton)
@eregon — I have tried start/end line/column extensively. It did not work at all for Rails or error highlight, and I spent too long on it to revisit it. Also, it has been rejected twice in this thread alone. If, regardless, you would lik...kddnewton (Kevin Newton)
We should make sure start line respects the line passed into eval (not sure if that was implicit, but wanted to be sure to call it out). For the heredocs, I agree that they should be omitted. We made that decision early with Prism bec...kddnewton (Kevin Newton)
We can't change this without breaking user code. Things like ``` irb(main):003> def resolve; SyntaxError; end => :resolve irb(main):004> begin; raise SyntaxError, 'lol'; rescue resolve; end => nil irb(main):005> begin; raise Argu...kddnewton (Kevin Newton)
The honest answer is, not really. It's probably fine to stay as is, and I would be okay with closing this. For context, I've been building a translation layer from RubyVM::AbstractSyntaxTree to Prism, hoping it might help with a migra...kddnewton (Kevin Newton)