Fix several hlint issues related with the use of parsed module without comments #2366
Conversation
This file contains 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
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.
The plugin was not using the
getParsedModuleWithCommentsso it was missing all info encoded in comments: pragmas, directives, etc and causing several issuesFixes HLint plugin ignores "ignore"s defined as {-# HLINT ... -#} annotations #638
Fixes HLint doesn't report "Unused LANGUAGE pragma" #2042
Fixes HLint reports incorrect redundant irrefutable pattern #2280
I was suspecting this so i added the regression tests in #2321 with the intent of fixing them in a ongoing pr, this one.
(I've included a minor correction of bullet lists suggested by markdown linting)