You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, function calls are definitely the part that's hardest to work through. I've taken a couple of attempts at trying to support "bare" function calls (like puts "test hello" or getter :my_attr), with no real success so far - precedence conflicts happen like crazy. I've been trying to pin down places where whitespace shouldn't be allowed to try to avoid some of the conflicts I see when I poke at it.
I wonder if it's worth trying to adapt the tree-sitter grammar for ruby here...could be worth a shot.
Hey @spencerwi I've been trying to get like
3.to_s
or[1,2,3].first
to work, and I think what needs to change issince I think you can call a method on the result of any expression (though this might be wrong).
This change causes precedent problems with
$assignment
, so I'm not sure if I'm on the right track. Do you have ideas on what should be done?The text was updated successfully, but these errors were encountered: