Ivan Kochurkin

Tests are failing, please take a look at https://github.com/antlr/grammars-v4/actions/runs/3114604472/jobs/5051646144

Unfortunately, it's still failing: https://github.com/antlr/grammars-v4/actions/runs/3129572326/jobs/5079043197#step:5:14653

Also, could you please add an example that covers suggested changes?

I don't think it's a problem, the rewritten rule doesn't simplify grammar. Also, you can use [Rule Element Labels](https://github.com/antlr/antlr4/blob/master/doc/parser-rules.md#rule-element-labels) to archive the same goal: ```g4 expression : multiplyingExpression (operator+=(PLUS |...

They don't look semantics errors: ``` SyntaxError: Unexpected token '^' SyntaxError: Unexpected token ';' ```

I have no objection of making the grammar more strict if it's possible.

Have you tried to use parse tree free processing strategy (`buildParseTrees = false`)? It allows creating AST during parsing using Listener without creating full parse tree. It saves a lot...

> How do I do this? I've not heard of this. ANTLR generates Parse Tree instead of AST, but the latest also can be generated by hand without generating Parse...

Could you please add a test sample to the examples dir?

Honestly, I don't think such description file is required at all. It's possible just to traverse directories and discover grammar files there. We have single pattern for grammar files and...