Open ap29600 opened 2 years ago
closed by #6
I am pretty sure this bug is still reproducible, as the grammar as defined in the repo is actually ambiguous. I suspect a proper fix would require that we define a subset of the grammar that is allowed between 'for'
and the matching '{'
, where the character '{'
is not allowed unless within unambiguous delimiters of some kind ('()', '[]'
)
The following code fails to parse:
the desired output should be:
actual output is: