-
Notifications
You must be signed in to change notification settings - Fork 382
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: backports for leanprover/lean4#4814 (part 1) #15245
Conversation
PR summary 5092be0756Import changes for modified filesNo significant changes to the import graph Import changes for all files
Declarations diffNo declarations were harmed in the making of this PR! 🐙 You can run this locally as follows## summary with just the declaration names:
./scripts/declarations_diff.sh <optional_commit>
## more verbose report:
./scripts/declarations_diff.sh long <optional_commit> The doc-module for |
section | ||
variable [Decidable Q] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one looks wrong, you're just adding an assumption.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously we were using an explicit Decidable P
, and the classical decidable instance for Q
. Surely this is not what was intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the explanation, I had not noticed the attribute [local instance 10] Classical.propDecidable
at the beginning of the file (which we should probably remove, but that's for another PR).
see #15245 Co-authored-by: Kim Morrison <[email protected]>
bors d+ |
✌️ semorrison can now approve this pull request. To approve and merge a pull request, simply reply with |
See #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
bors merge |
The new variables inclusion mechanism leanprover/lean4#4814 is going to require many changes to Mathlib. Some of these changes are to make sure typeclass hypotheses are not unnecessarily included. This is achieved either by using `section` to bound `variable [...]`, using `variable ... in`, or reordering theorems. (I think you can see all three being using here.) Other changes require adding `include ...` to include variables that the new mechanism won't automatically include. These changes can't be backported to master, and instead are accumulating on the `lean-pr-testing-4814` branch.
Pull request successfully merged into master. Build succeeded: |
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
See #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
The new variables inclusion mechanism leanprover/lean4#4814 is going to require many changes to Mathlib. Some of these changes are to make sure typeclass hypotheses are not unnecessarily included. This is achieved either by using `section` to bound `variable [...]`, using `variable ... in`, or reordering theorems. (I think you can see all three being using here.) Other changes require adding `include ...` to include variables that the new mechanism won't automatically include. These changes can't be backported to master, and instead are accumulating on the `lean-pr-testing-4814` branch.
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
See #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
The new variables inclusion mechanism leanprover/lean4#4814 is going to require many changes to Mathlib. Some of these changes are to make sure typeclass hypotheses are not unnecessarily included. This is achieved either by using `section` to bound `variable [...]`, using `variable ... in`, or reordering theorems. (I think you can see all three being using here.) Other changes require adding `include ...` to include variables that the new mechanism won't automatically include. These changes can't be backported to master, and instead are accumulating on the `lean-pr-testing-4814` branch.
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
see #15245 Co-authored-by: Ruben Van de Velde <[email protected]>
The new variables inclusion mechanism leanprover/lean4#4814 is going to require many changes to Mathlib.
Some of these changes are to make sure typeclass hypotheses are not unnecessarily included. This is achieved either by using
section
to boundvariable [...]
, usingvariable ... in
, or reordering theorems. (I think you can see all three being using here.)Other changes require adding
include ...
to include variables that the new mechanism won't automatically include. These changes can't be backported to master, and instead are accumulating on thelean-pr-testing-4814
branch.