Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development planning, Milestone 3 #10

Open
2 of 5 tasks
mike-lischke opened this issue Feb 11, 2024 · 1 comment
Open
2 of 5 tasks

Development planning, Milestone 3 #10

mike-lischke opened this issue Feb 11, 2024 · 1 comment

Comments

@mike-lischke
Copy link
Owner

mike-lischke commented Feb 11, 2024

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).

@mike-lischke
Copy link
Owner Author

🎉 The optimized antlr4ng runtime performs really well. It's faster in most aspects than any of the other TS/JS runtimes (antlr4, antlr4ts, antlr4wasm).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant