Trim non-critical runtimes about antlr5 HOT 5 CLOSED

Currently I don't see big need in trimming at least if it doesn't affect development process (we can do it later). But performance of TypeScript definitely needs to be improved because it negatively affects development experience and remote built: antlr/antlr4#4229

from antlr5.

The need is to:

• have our CI focus on runtimes relevant for ANTLR 5
• reduce refactoring effort when switching to add-ons

from antlr5.

Currently it's definitely not possible to get rid of Java runtime because tool-testsuite depends on it. Also, Java has some tests that other runtimes don't have (at first they should be ported or removed).

But I'm not sure about current TypeScript runtime. If we are going to use Kotlin for generating WA, I suppose future TypeScript wrapper will have almost nothing in common with the current code. It could increase refactoring effort if keep TypeScript now. Also, TypeScript tests currently are slow (Kotlin tests are also slow but Kotlin is crucial).

from antlr5.

Yes the plan is to drop all targets and runtimes except Java (reference runtime and required for the tool), Kotlin, and TypeScript without tests.
We need to keep TypeScript around a bit as a basis for the generated TypeScript parser wrapper (wrapping WebAssembly parser generated from generated Kotlin code, itself linked with the WebAssembly runtime generated from Kotlin).

from antlr5.

Fixed with #17

from antlr5.