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
Currently the whole grammar of Rune is defined in a single huge xtext file. This in turn leads to large derived Java classes, both generated (parser, sequencer, ...) and manually written (validator, formatter, ...).
Splitting up our grammar file can improve modularity, leading to more maintainable code. Additionally, projects using jacoco will stop seeing MethodTooLargeExceptions while building when they have the Rune DSL as a dependency.
I would propose the following splitting:
Rune types.
Rune expressions (extends Rune types).
Rune functions (extends Rune expressions).
Rune reporting (extends Rune expressions).
Rune translate (extends Rune expressions).
Rune (top layer interface, extends everything).
The text was updated successfully, but these errors were encountered:
Currently the whole grammar of Rune is defined in a single huge xtext file. This in turn leads to large derived Java classes, both generated (parser, sequencer, ...) and manually written (validator, formatter, ...).
Splitting up our grammar file can improve modularity, leading to more maintainable code. Additionally, projects using jacoco will stop seeing
MethodTooLargeException
s while building when they have the Rune DSL as a dependency.I would propose the following splitting:
The text was updated successfully, but these errors were encountered: