There are a bunch of tokens that we decided to drop, but C-family languages use them extensively:
%
||
&&
!
This causes interesting errors being reported. For example, if (x == 0 || x == 1) will report, that it expects a ) instead of |.
We could improve error messages, recover (and tree-shapes) by lexing these tokens but report a parse-error.
There are a bunch of tokens that we decided to drop, but C-family languages use them extensively:
%||&&!This causes interesting errors being reported. For example,if (x == 0 || x == 1)will report, that it expects a)instead of|. We could improve error messages, recover (and tree-shapes) by lexing these tokens but report a parse-error.