Closed gonglinyuan closed 1 year ago
Thanks for the fix!
I'm going to have to revert this as it's causing the following regression:
Sprite mySprite = GetNode<Sprite>("Sprite");
Should be an invocation_expression
on the right-hand side but this change is causing it to be an (incorrect) binary_expression
now.
Not sure how we didn't have test coverage for this scenario.
I'm going to have to revert this as it's causing the following regression:
Sprite mySprite = GetNode<Sprite>("Sprite");
Should be an
invocation_expression
on the right-hand side but this change is causing it to be an (incorrect)binary_expression
now.Not sure how we didn't have test coverage for this scenario.
The expression
(a) && b
in this statement:was mistakenly parsed as a cast expression of type
a
applied to&&b
, which is variableb
dereferenced via&
twice. However, it should have been parsed just as a logical_and expression.This PR changed the grammar to fix this issue.