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

Suggest: '(& f)' -> 'f' #1274

Closed
wants to merge 1 commit into from
Closed

Suggest: '(& f)' -> 'f' #1274

wants to merge 1 commit into from

Conversation

mlang
Copy link

@mlang mlang commented Aug 6, 2021

Thanks for the pull request!

By raising this pull request you confirm you are licensing your contribution under all licenses that apply to this project (see LICENSE) and that you have no patents covering your contribution.

If you care, my PR preferences are at https://github.com/ndmitchell/neil#contributions, but they're all guidelines, and I'm not too fussy - you don't have to read them.

Copy link
Owner

@ndmitchell ndmitchell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the hint! I thought we already had this one included in the standard defaults with

- warn: {lhs: (Data.Function.& f), rhs: f, name: Redundant Data.Function.&}
- is that not firing for you for some reason?

@mlang
Copy link
Author

mlang commented Aug 6, 2021 via email

ndmitchell added a commit that referenced this pull request Aug 8, 2021
@ndmitchell
Copy link
Owner

I've removed the Data.Function qualification. At the beginning & was a bit of a rare function, so I wanted to be careful about when it triggered. Now it's much more common, so I think relaxing it makes a lot more sense. Thanks for the suggestion!

@ndmitchell ndmitchell closed this Aug 8, 2021
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