-
Notifications
You must be signed in to change notification settings - Fork 297
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
chore(category_theory/limits): unify naming of lemmas related to the (co)lim functor #2040
Conversation
@@ -616,16 +616,16 @@ def lim : (J ⥤ C) ⥤ C := | |||
|
|||
variables {F} {G : J ⥤ C} (α : F ⟶ G) | |||
|
|||
@[simp, reassoc] lemma lim.map_π (j : J) : lim.map α ≫ limit.π G j = limit.π F j ≫ α.app j := | |||
@[simp, reassoc] lemma limit.map_π (j : J) : lim.map α ≫ limit.π G j = limit.π F j ≫ α.app j := |
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.
I think the reason it was called lim.map_pi
is that the statement starts with lim.map \alpha ...
. Hence it follows the naming conventions, and I'm inclined to leave it the way it was...
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 makes sense, but I feel that if the name lim.map_pi
is used, then the name lim.map_pre
should also be used instead of limit.map_pre
. On the other hand, limit.map_pre'
would still be correct, so a series of very closely related lemmas would have different prefixes.
As someone who tried to use these lemmas, I found the current situation to be very confusing, and I chose this way of unification because it looked like it would require the fewest changes, but I'd be happy to change the PR to instead rename limit.map_pre
(and maybe limit.map_post
?).
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.
@TwoFX Fair enough, I agree with the confusion. I think that limit.map_pre
is actually the one that is "violating" the naming convention. If you want to PR those changes, that would be nice.
@jcommelin I have adapted the names of the lemmas as discussed. Note that in this version the naming is not consistent across duals. For example, we have |
Hmmm... I agree that that is also confusing. I think being consistent across duals is maybe more important than other considerations. @semorrison do you have some helpful advice? |
Let's just name everything with (The underlying confusion here is that I decided to use the shortened So --- @TwoFX, would you mind restoring your PR to the original state? |
Done. |
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.
Cool, I agree with Scott, after second thought. It's on the merge queue.
…munity#2040) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
…munity#2040) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
lim.map_π
was the only lemma of the formlim.*
rather thanlimit.*
, and I do not see any way it differs fromlimit.map_pre
and others that could justify the different naming.