Enforce Scala 2 compatible syntax #1677
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In past PRs we've been asking contributors to use Scala 2 compatible syntax. On this PR I'm starting to enforce these choices using scalac and scalafix.
Most PureConfig code is cross-compiled against Scala 2.12, 2.13 and 3 and in those we have no choice but to use syntax compatible with all versions. Some Scala3-only code could technically use the new syntax, but this would create a discrepancy in code style that I'd rather avoid as long as we can (i.e. until Scala 3 drops support for some Scala 2 syntax).