Skip to content

merge queue: embarking master (eec643a), #11814 and #11808 together#11831

Closed
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/90b8444265
Closed

merge queue: embarking master (eec643a), #11814 and #11808 together#11831
mergify[bot] wants to merge 4 commits into
masterfrom
mergify/merge-queue/90b8444265

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 15, 2026

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch master (eec643a), #11814 and #11808 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #11808.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for 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

Required conditions to stay in the queue:

---
checking_base_sha: 6d2653f4d899b10f85f13f7edc68dec21a1a088f
previous_failed_batches: []
pull_requests:
  - number: 11808
    scopes: []
scopes: []
...

leana8959 and others added 4 commits May 13, 2026 13:57
Add -Wredundant-constraints ghc flag to ghc-optionss.config.

HasVerbosity, HasCallStack and WithCallStack constraints are not
touched. -Wno-redundant-constraints is added for these modules

FieldGrammar allows instances to specify a constraint that its methods
should follow. ParsecFieldGrammar is an instance of FieldGrammar
(when using the grammar as a parser) that c is instantiated as Parsec;
PrettyFieldGrammar is also an instance of FieldGrammar (when using
the grammar as a printer) that c is instantiated as Pretty.

With that in mind:

    For ParsecFieldGrammar, Parsec (List FSep Token String) holds.
    For PrettyFieldGrammar, Pretty (List Fsep Token String) holds.

I removed this and all tests still pass, so this constraint is not
needed (i.e. we actually don't need to parse or print a List FSep Token
String).
@mergify mergify Bot closed this May 15, 2026
@mergify mergify Bot deleted the mergify/merge-queue/90b8444265 branch May 15, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants