Skip to content

Follow hlint suggestion: redundant <$>#11744

Merged
mergify[bot] merged 1 commit intohaskell:masterfrom
cabalism:hlint/redundant-fmap
Apr 17, 2026
Merged

Follow hlint suggestion: redundant <$>#11744
mergify[bot] merged 1 commit intohaskell:masterfrom
cabalism:hlint/redundant-fmap

Conversation

@philderbeast
Copy link
Copy Markdown
Collaborator

See #9110. Discharges and no longer ignores HLint's "redundant <$>" suggestion so that this will be suggested by our CI linting. A lot of these replace a sequence of f <$> g <$> etc with f . g <$> etc.

I'll squash commits before applying the merge label if this pull request is approved.


  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@philderbeast philderbeast force-pushed the hlint/redundant-fmap branch 2 times, most recently from 517581b to eaf2db7 Compare April 15, 2026 10:01
@philderbeast philderbeast added the merge me Tell Mergify Bot to merge label Apr 15, 2026
- Satisfy fourmolu
- Update hlint counts with hlint --default
@philderbeast philderbeast force-pushed the hlint/redundant-fmap branch from eaf2db7 to 05eb64f Compare April 15, 2026 17:56
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Apr 15, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Apr 17, 2026

Merge Queue Status

This pull request spent 2 hours 52 seconds in the queue, including 1 hour 50 minutes 5 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

mergify bot added a commit that referenced this pull request Apr 17, 2026
@mergify mergify bot merged commit a3a67ab into haskell:master Apr 17, 2026
175 checks passed
@mergify mergify bot removed the queued label Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants