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
Recently I had built a project with Antlr 4.9.2. It is all good when I made lexer and parser and it didn't show any errors from the IDE plugin. But when I run a demo and test, the error ERROR AssertionError [ERR_ASSERTION]: false == true has been showed on the console.
It ran when I retried the steps again tho...
Trace
I noticed that it points to the rule nonsenseParam in my project while other rules are fine. And the definition of nonsenseParam rule is as follows.
It used not operator in parser.
This operator is rarely used in the parser but is available. via antlr4/parser-rules
My project was used for three target languages --- TypeScript, Swift and Java. The Swift and Java version of generated parser and lexer are fine. Cuz they were generated by the official antlr4 runtime. So I reckon it is the issue of antlr4ts.
The text was updated successfully, but these errors were encountered:
Situation
Recently I had built a project with Antlr 4.9.2. It is all good when I made lexer and parser and it didn't show any errors from the IDE plugin. But when I run a demo and test, the error
ERROR AssertionError [ERR_ASSERTION]: false == true
has been showed on the console.It ran when I retried the steps again tho...
Trace
I noticed that it points to the rule
nonsenseParam
in my project while other rules are fine. And the definition ofnonsenseParam
rule is as follows.It used
not
operator in parser.My project was used for three target languages --- TypeScript, Swift and Java. The Swift and Java version of generated parser and lexer are fine. Cuz they were generated by the official antlr4 runtime. So I reckon it is the issue of antlr4ts.
The text was updated successfully, but these errors were encountered: