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
Groovy's optional parentheses for function calls have created an absolute nightmare.
For example, String foo and print foo should be parsed differently.
I noticed my parser fails on def x = foo "bar". To fix this, I'm trying to allow juxt_function_calls as _expressions. But that leads to a whole host of other ambiguities:
x ? f y:b : z // not ambiguous but hard to parse once you see the first colon
f y:b ? ... // is it (f y:b) ? ... or f y:(b ? ...)
a b, c ? d : e // is it (a b, c) ? d : e or a b, (c ? d : e)
and if I solve them by adding conflicts or trying to tweak precedence for map_item and ternary, all the tests break.
I feel like i need to redo the whole juxt_function_call thing... but I'm not sure how
The text was updated successfully, but these errors were encountered:
Groovy's optional parentheses for function calls have created an absolute nightmare.
For example,
String foo
andprint foo
should be parsed differently.I noticed my parser fails on
def x = foo "bar"
. To fix this, I'm trying to allow juxt_function_calls as _expressions. But that leads to a whole host of other ambiguities:and if I solve them by adding conflicts or trying to tweak precedence for map_item and ternary, all the tests break.
I feel like i need to redo the whole juxt_function_call thing... but I'm not sure how
The text was updated successfully, but these errors were encountered: