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
Having workers be written in Scala instead of Java presents multiple advantages:
Most of the repository’s compiled code is written in a single programming language
This reduces the learning curve for a new contributor
Many of the rule phases can be tested on the ruleset itself
Every rule phase that doesn't run Scala code would be run when we the workers themselves are built, assuming we do so via a set of bootstrap rules. This includes most phases, with the notable exception of the compile phase. If there's something wrong with one of those phases, we'll detect it, because the workers will fail to build. This enables bugs and developer experience regressions to be caught earlier.
The benefits of Scala are inherited, which include:
Safety
Conciseness
Expressiveness
Arguably superior object-oriented programming features
See the proposal for more information.
The text was updated successfully, but these errors were encountered:
This issue is part of a broader proposal to merge some of the features in
lucidsoftware/rules_scala into this ruleset.
The tracking issue for this effort
The relevant proposal section.
Having workers be written in Scala instead of Java presents multiple advantages:
Most of the repository’s compiled code is written in a single programming language
Many of the rule phases can be tested on the ruleset itself
compile
phase. If there's something wrong with one of those phases, we'll detect it, because the workers will fail to build. This enables bugs and developer experience regressions to be caught earlier.The benefits of Scala are inherited, which include:
See the proposal for more information.
The text was updated successfully, but these errors were encountered: