HLint: use == and redundant maybe#11477
Open
philderbeast wants to merge 1 commit intohaskell:masterfrom
Open
Conversation
sebright
approved these changes
Feb 12, 2026
- Update hlint --default counts - Follow hlint suggestion: use == - Follow hlint suggestion: redundant maybe - Remove redundant brackets
philderbeast
force-pushed
the
hlint/use-eq
branch
from
391c13f to
44c4980
Compare
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.
See #9110. Discharges and no longer ignores the "Use ==" and "Redundant maybe" suggestions so that these will be suggested by our CI linting. After these changes, the code is simpler.
I'll squash commits before applying the merge label if this pull request is approved.