This repository was archived by the owner on Nov 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
too slow.. #20
Comments
Thanks for measuring and reporting - I haven't done it in a while, but it used to be around ~15-20%, but it had one compiler phase fewer, and the abstract interpreter was not as big as it is now (I suspect most of the time is spent here). Right now the whole analysis runs, regardless of enabled/disabled checks, so there's obviously a lot of room for optimisation - I hope to find the energy to work on that on sunday. |
Merging issue with #39 |
Is it possible to run Linter not on every compile - maybe define a |
It's not done in Linter itself (I would have to make an extra sbt plugin - I'll get around to that someday :)), but there is an example of doing this in your sbt config here. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
the plugin impacts compilation time quite severely
for me it goes up from about 300 secs to about 600
even enabling just one check, eg enable-only:UnlikelyEquality still gives me about 600 secs
The text was updated successfully, but these errors were encountered: