Hlint: suggest nub alternative#11825
Conversation
a350dda to
d7a010b
Compare
d7a010b to
1d0950b
Compare
1d0950b to
d1dcf19
Compare
- Use single letter variables with hlint rules - Only suggest ordNub - Add growth rate note - Include necessary imports - Follow hlint suggestion: use ordNub - Follow hlint suggestion: use ordNub in tests - Satisfy hlint: use fewer imports - Add @SInCE annotations for added Ord instances
d1dcf19 to
64d8543
Compare
|
@mergify queue |
Merge Queue Status
This pull request spent 1 hour 34 minutes 47 seconds in the queue, including 1 hour 24 minutes 11 seconds running CI. Waiting for any of
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
|
@mergify queue |
Merge Queue Status
This pull request spent 11 minutes 57 seconds in the queue, including 40 seconds running CI. Waiting for
All conditions
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks:
HintYou may have to fix your CI before adding the pull request to the queue again. |
|
GitHub CI is being flaky: |
|
@mergify queue |
Merge Queue Status
This pull request spent 1 hour 55 minutes 42 seconds in the queue, including 1 hour 44 minutes 11 seconds running CI. Required conditions to merge
|
Fixes #11824.
When fired, this suggestion renders as:
I didn't correct
O(n log n)to theO(n log d)from containers haddocks fornubOrd. Neither did I suggest using that equivalent function from containers. For that, I raised #11826.I had to add
Ordinstances to a few data types,BuildTargetandMatchError. I changed theEqconstraint to anOrdconstraint forfindMatchandnubMatches.I left a note in
.hlint.yamlto only use single letter variables in rules.I used a separate commit for changes to tests but on approval will squash all commits before adding the
merge melabel.