build.sbt: Rework scalacOptions #21
Merged
Conversation
This file contains hidden or 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
Add scalacOptions which have proved useful in the ScalaNative build itself. The options here are not exactly the same. For example, this build uses, rightly, -Yno-unused-imports. Tested manually. No fatal or warning messages were found whilst building the current code base. Enabling these options should help keep deprecation warnings & such from unintentionally creeping in as the code base evolves. No documentation impact.
lolgab
approved these changes
Apr 17, 2020
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.
Add scalacOptions which have proved useful in the ScalaNative build
itself. The options here are not exactly the same. For example,
this build uses, rightly, -Yno-unused-imports.
Tested manually. No fatal or warning messages were found whilst building
the current code base. Enabling these options should help keep deprecation
warnings & such from unintentionally creeping in as the code base
evolves.
No documentation impact.