-
Notifications
You must be signed in to change notification settings - Fork 299
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 by Bors] - chore(data/finsupp/basic): make arguments explicit #14551
Conversation
This follow the pattern that arguments to an `=` lemma should be explicit if they're not implied by other arguments.
46e754c
to
be0ab8d
Compare
I don't think this is a rule at all. There are many examples where it's more convenient to have it implicit. See e.g. Is there a single occurrence of |
I'd argue that the arguments should be explicit in your two examples too; it's a lot harder to target a specific rewrite if you can't fill out any of the unbound variables. |
Maybe you're right. bors merge |
👎 Rejected by label |
good bot bors d+ |
✌️ eric-wieser can now approve this pull request. To approve and merge a pull request, simply reply with |
Yes, I agree that non-equalities typically have different rules. |
bors merge |
This follow the pattern that arguments to an `=` lemma should be explicit if they're not implied by other arguments.
Pull request successfully merged into master. Build succeeded: |
This follow the pattern that arguments to an `=` lemma should be explicit if they're not implied by other arguments.
This follow the pattern that arguments to an
=
lemma should be explicit if they're not implied by other arguments.