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.
Adds the scala inliner/optimizer for Scala 2 versions. The inline options that were picked are the ones determined to be safe for libraries (which sbt-library-management is).
The reasons for adding this is because
One thing to note about the inliner is can cause development hitches locally (i.e. with Scala's incremental compiler). The easiest way to get around this would be to put the inliner behind an argument flag so that CI turns on the inliner (both for PR checks and for publishing) but by default inliner is off so that it doesn't mess with local development. The reason I didn't do this is because it appears that publishing is still done manually on someones machine (I can't see a github action for publishing) and hence it would be easy to forget to enable the inliner when publishing a new version of this library.
I guess if the standard "push tag to trigger a CI" publishing is added to this repo I can then update the PR with this suggestion (I would actually make the inliner an `AutoPlugin).