Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

avoid incomplete record selection warning (backport #10403) #10450

Merged
merged 1 commit into from
Nov 7, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 12, 2024

Per SPJ suggection.

Closes: #10402

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

  • 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). (doesn't fix CI but GHC HQ will want a 3.14 backport at minimum)

This is an automatic backport of pull request #10403 done by [Mergify](https://mergify.com).

@mergify mergify bot added the backport label Oct 12, 2024
@geekosaur geekosaur force-pushed the mergify/bp/3.14/pr-10403 branch from 54268ee to db896cd Compare October 29, 2024 19:22
@ulysses4ever
Copy link
Collaborator

This looks trivial enough to merge without additional litigation, doesn't it?

@ulysses4ever ulysses4ever added the merge me Tell Mergify Bot to merge label Nov 7, 2024
Per SPJ suggection.

Closes: #10402
(cherry picked from commit b1798b5)
@Mikolaj Mikolaj force-pushed the mergify/bp/3.14/pr-10403 branch from db896cd to 505f875 Compare November 7, 2024 15:57
@mergify mergify bot merged commit c7abe0a into 3.14 Nov 7, 2024
53 checks passed
@mergify mergify bot deleted the mergify/bp/3.14/pr-10403 branch November 7, 2024 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport merge me Tell Mergify Bot to merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants