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
This list covers the next steps after having both a full TS runtime and the full runtime/api tests ported to TS.
Consolidate the TS runtime (consistent naming of properties, remove leading underscores in properties, really make private what is private, convert data-only classes to interfaces etc.).
Optimize the runtime to get it as close as possible to the old JS runtime execution speed.
Do initial port of the Java ANTLR4 tool to TS and make it build.
Get the TS tool port to work properly.
Release the tool as node package.
The first two steps are handled in an own branch, which later gets released as a new major version (because of API changes).
The text was updated successfully, but these errors were encountered:
🎉 The optimized antlr4ng runtime performs really well. It's faster in most aspects than any of the other TS/JS runtimes (antlr4, antlr4ts, antlr4wasm).
This list covers the next steps after having both a full TS runtime and the full runtime/api tests ported to TS.
The first two steps are handled in an own branch, which later gets released as a new major version (because of API changes).
The text was updated successfully, but these errors were encountered: