-
Notifications
You must be signed in to change notification settings - Fork 396
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: fix outdated ext
porting notes
#17810
Conversation
PR summary dd52b4e769Import 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 |
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.
🎉
@@ -38,7 +38,6 @@ such that `f ≫ retraction f = 𝟙 X`. | |||
Every split monomorphism is a monomorphism. | |||
-/ | |||
/- Porting note(#5171): removed @[nolint has_nonempty_instance] -/ | |||
/- Porting note: `@[ext]` used to accept lemmas like this. Now we add an aesop rule -/ | |||
@[ext, aesop apply safe (rule_sets := [CategoryTheory])] | |||
structure SplitMono {X Y : C} (f : X ⟶ Y) where |
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.
Should the aesop
tag be removed accordingly? What does it even do, when applied to a structure?
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.
So I went as far as checking the aesop
source code and as far as I can tell, no idea what it's supposed to mean 🤷. Looks like removing the attribute doesn't break anything either.
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 digging! @JLimperg, maybe there should be a check in aesop that one is not tagging a structure?
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.
The rule takes the structure
and register it as a rule with conclusion Type _
, naturally. 🙂 But yes, Aesop should warn about this. leanprover-community/aesop#172
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, this is great. Feel free to maintainer merge
on my behalf once Yael's question about aesop has been resolved.
I went through all porting notes mentioning `ext` and fixed / removed those that no longer apply.
2e1ebb3
to
dd52b4e
Compare
Thanks! |
I went through all porting notes mentioning `ext` and fixed / removed those that no longer apply.
Pull request successfully merged into master. Build succeeded: |
ext
porting notesext
porting notes
I went through all porting notes mentioning
ext
and fixed / removed those that no longer apply.