smythi93 / jast / 27904708037

100%

Build Type

push

github

Committed by smythi93

Commit Message

Fix parsing of postfix on object creation (issue #1); re-enable C++ parser

`new X().run()` failed to parse ("mismatched input '.' expecting ';'")
because `NEW creator` lived in the typeExpression rule (precedence below
primary), so a completed object creation could never take a trailing
'.', '[' or '::'. Move `NEW creator` into primary as a labeled
ObjectCreationExpression, regenerate the Python and C++ parsers, and add
the matching converter visitor.

The unparser now emits `new X().run()` without redundant parentheses
(NewObject is self-delimiting, so it gets PRIMARY precedence). NewArray
keeps TYPE precedence since `(new int[3])[0]` differs from `new int[3][0]`.

Re-enable the C++ accelerator:
- restore the legacy/USE_CPP_IMPLEMENTATION dispatch in _parse.py
- make the speedy-antlr error listener raise instead of swallowing errors
- generate accelerator entry rules for every ParseMode, not just
  compilationUnit, and rebuild the binding/translator
- handle ctx.start == None in _get_location_rule (empty rules report no
  start token under the C++ runtime)

Also fix regressions from the numeric-literal/interleave changes:
- interleave treats None as empty (receiver with no identifiers)
- update literal tests for the new suffix handling (42L, 3.14f) and add
  raw-text coverage

Add tests for object creation followed by member access, chained calls,
and array-creator subscripting, plus the exact scenarios from the issue:
the main() declaration snippet and the complete Solution program
(tests/data/issue_1_solution.java).

Coverage Stats

12 of 12 new or added lines in 3 files covered. (100.0%)

1 existing line in 1 file now uncovered.

3368 of 3369 relevant lines covered (99.97%)

1.0 hits per line