-
-
Notifications
You must be signed in to change notification settings - Fork 397
simplify hlint plugin Cabal descriptor #2867
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
To make |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your reasoning sounds good to me. I'm confused about the ghc-lib comment, though. If there's no reason not to use ghc-lib instead of ghc, why isn't hlint
doing that?
Ah, ignore the last comment, I just read the linked issue in hlint. |
fde6323
to
9baf475
Compare
- the ghc-lib flag is unnecessary, we want to use ghc-lib always for maximum compatibility - the hlint34 flag is unnecessary, we can trust cabal to use the right version
While working on #2866 I noticed that
hls-hlint-plugin
requires per-ghc-version flags. This preventscabal install haskell-language-server
from working across ghc versions.I think we can get rid of these flags:
ghc-lib
flag is unnecessary, there is no downside to using ghc-lib always for maximum compatibilityhlint34
flag is unnecessary, cabal should be able to use the right version