Use Scalafix for organizing imports#121
Merged
Merged
Conversation
withLocalCleanup gave a cyclic import error after cleaning up imports, showing that there was something fishy before. The error can be avoided by declaring a function directly in the package object, which references an impl function.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR proposes to add scalaFix to the project, for the purpose of organizing imports.
In addition to adding scalafix, imports are organized and a problem with cyclic dependencies that made the compiler stumble is fixed. The problem is with the
MemoryHelper.withLocalCleanup, which is now split into an imp function and a call directly from package.scala, such that the calldimwit.withLocalCleanupworks unchanged.