ryanprince / earley-intersection-js Goto Github PK

It would be great if the system could read and write FSAs that are encoded in an open standard.

If support gets added for one, some examples could be added with 3rd party modules. E.g., graphical renderings of the inputs and outputs.

It would be great if the system could read and write CFGs that are encoded in an open standard.

If support gets added for one, some examples could be added with 3rd party modules. E.g., graphical renderings of the inputs and outputs.

What is an unobtrusive way of making the weights optional for users of the module?

Looking ahead, are the open standards for weighted CFGs more limited than for unweighted ones?

Aiming for two benefits:

• Fix bugs that are discovered while adding static typing.
• Make it easier to add future performance and feature improvements.

Prioritize the module's compatibility with standard JavaScript environments.

It would also be nice for TypeScript users to benefit from the type definitions.

Ideas:

• A richer type system would allow for more efficient data representations while enhancing code readability.
• What benchmarks could be used?
• Can inefficient performance test cases be identified and improved?