Skip to content

Follow hlint suggestion: use infix #11143

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

Merged
merged 1 commit into from
Aug 12, 2025
Merged

Conversation

philderbeast
Copy link
Collaborator

@philderbeast philderbeast commented Aug 9, 2025

See #9110. Discharges and no longer ignores the "Use infix" warning so that it will be picked up by our CI linting.

A follow on from #11135, from a code review suggestion from @ulysses4ever to use notElem infix, #11135 (comment).

After following the suggestions, I made a couple of additional changes, adding an extensionIn function and reusing the hasThreaded function.

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 changed the title Hlint/use infix Follow hlint suggestion: use infix Aug 9, 2025
- Follow hlint suggestion: Use infix for elem and notElem
- Follow hlint suggestion: Use infix for isPrefixOf
- Follow hlint suggestion: Use infix for set ops, union and intersect
- Add extensionIn
- Reuse hasThreaded
@philderbeast philderbeast added the merge me Tell Mergify Bot to merge label Aug 9, 2025
@mergify mergify bot added the ready and waiting Mergify is waiting out the cooldown period label Aug 9, 2025
@philderbeast
Copy link
Collaborator Author

@mergify refresh

Copy link
Contributor

mergify bot commented Aug 11, 2025

refresh

✅ Pull request refreshed

@philderbeast
Copy link
Collaborator Author

Does the bot refresh reset the countdown timer or is this pull request stuck? If the former can I please add [merge delay passed] label?

@ulysses4ever
Copy link
Collaborator

Quick glance makes me think you said "mergify refresh" a tiny bit before the 48 hours from the last push lapsed. Maybe it decided to reset the timer then. I'd wait more. Sadly, there's no reliable way to check the timer, afaik.

@philderbeast
Copy link
Collaborator Author

Maybe it decided to reset the timer then.

Thanks @ulysses4ever. Yes that's what I'm thinking too. At 3 days now, we've definitely passed the 2 day delay.

@geekosaur
Copy link
Collaborator

@Mergifyio queue

Copy link
Contributor

mergify bot commented Aug 12, 2025

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at ff7c123

mergify bot added a commit that referenced this pull request Aug 12, 2025
@mergify mergify bot merged commit ff7c123 into haskell:master Aug 12, 2025
174 of 177 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

4 participants