Releases: mike-lischke/antlr4-c3
New Point Release
-
PR #80 Candidate token's follow TokenList is inaccurate when the candidate's origin is ambiguous
-
PR #135 Add GitHub Workflow for Java port
-
PR #137 Add Clang-Format and Clang-Tidy checks
-
PR #140 C++ port light refactororing and bug fix
-
PR #146 Change C++ port public API
-
PR #147 Run C++ tests in random order
-
PR #148 Make global mutable state thread_local
-
PR #149 Remove FollowSet cache dependency on ignoredTokens
-
PR #160 Make C++ port debug output more like TS
-
PR #161 Use grammars from the TS project for C++ port testing
-
PR #163 Remove generated parsers
-
PR #164 Provide support for Dart language
-
PR #166 Replace isPrecedenceRule with isLeftRecursive
-
Fixed Bug #94 Autocompleting empty string causes error (in PR #95)
-
Fixed Bug #108 Java port-> NPE happen when followSets contains FollowSetWithPath with null following member (in PR #109)
-
Fixed Bug #139 Make C++ port thread safe
-
Fixed Bug #162 Grammar and generated files can be inconsistent (in PR #163)
-
Fixed Bug #165 isPrecedenceRule is required to be required by CodeCompletionCore but seems to be missing from antlr4ng (in PR #166)
New Minor Release
- Switched to a new major version of the antlr4ng runtime (3.0.0).
- Fixed issue #96 Add .cjs output to package
New point release
Stop bundling 3rd party libraries in the own lib bundle. This is not only unnecessary (these deps are installed with all the other dependencies in a target project), but can cause trouble if a depenent project uses 2 different versions of such a bundled 3rd party lib.
New point release
- Fixed bug #93 Add command to esbuild (stop including 3rd party libs in bundle).
- Updated dependencies.
New point release
Upgraded dependencies
v3.3.3
Updated dependencies, which required some changes
New Minor Release
Updated dependencies and changed package building to use esbuild.
Adjustments for latest antlr4ng
- Updated c3 code.
- Updated Jest settings to run ESM + TS tests.
Finished switch from antlr4ts to antlr4ng
New Point Release
No functional changes compared to v3.1.0, I just forgot to update the readme 🙄