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] - feat(category_theory/limits/shapes/multiequalizer): Multi(co)equalizers #10169
Conversation
@[nolint has_inhabited_instance] | ||
structure multicospan_index (C : Type u) [category.{v} C] := | ||
(α β : Type v) | ||
(f s : β → α) |
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.
These names are not very mnemonic. Also, should α
and β
be bundled?
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 I'll switch them to L
resp. R
(for left resp. right). Is there a particular reason you think they should not be bundled?
In the (hopefully near?) future where we have pseudofunctors, I can imagine wanting to talk about the category of multicospan_index
s and to a morphism in this category, obtain a functor between walking_multicospan
s which fit together into a pseudofunctor. This might be an argument for bundling.
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 renamed \alpha -> L
and \beta -> R
, also f -> fst_to/fst_from
and s -> snd_to/snd_from
.
Could there / should there be isomorphisms from the |
Good idea. I'll try to add that soon. |
On second thought, I think it would be too much additional work to do this properly, so I think it would be better to leave this for a future PR. I added a comment under the |
Did you run into any obstacle when trying to do so? If not, and that it is merely time-consuming, I could try do it since I would probably need these results when gluing. An alternative would be to develop API about multicoequalizers in |
There is no real difficulty, what to do it properly would require the following:
So the main obstacle is time, and that all of this would probably be too much for a single PR :) |
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 🎉
bors merge
bors r- |
Canceled. |
bors d+ |
✌️ adamtopaz can now approve this pull request. To approve and merge a pull request, simply reply with |
bors r+ |
…rs (#10169) This PR adds another special shape to the limits library, which directly generalizes shapes for many other special limits (like pullbacks, equalizers, etc.). A `multiequalizer` can be thought of an an equalizer of two maps between two products. This will be used later on in the context of sheafification. I don't know if there is a standard name for the gadgets this PR introduces. I would be happy to change the names if needed.
Pull request successfully merged into master. Build succeeded: |
…rs (#10169) This PR adds another special shape to the limits library, which directly generalizes shapes for many other special limits (like pullbacks, equalizers, etc.). A `multiequalizer` can be thought of an an equalizer of two maps between two products. This will be used later on in the context of sheafification. I don't know if there is a standard name for the gadgets this PR introduces. I would be happy to change the names if needed.
This PR adds another special shape to the limits library, which directly generalizes shapes for many other special limits (like pullbacks, equalizers, etc.). A
multiequalizer
can be thought of an an equalizer of two maps between two products. This will be used later on in the context of sheafification.I don't know if there is a standard name for the gadgets this PR introduces. I would be happy to change the names if needed.