This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 299
[Merged by Bors] - feat(order/lattice): add complete_semilattice_Sup/Inf #6797
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
semorrison
added
the
awaiting-review
The author would like community review of the PR
label
Mar 21, 2021
Co-authored-by: Bryan Gin-ge Chen <bryangingechen@gmail.com>
2 tasks
Looks reasonable to me bors d+ Probably worth merging master ifrst just in case this has gone stale, unless bors is idle anyway |
✌️ semorrison can now approve this pull request. To approve and merge a pull request, simply reply with |
bryangingechen
added
delegated
The PR author may merge after reviewing final suggestions.
and removed
awaiting-review
The author would like community review of the PR
labels
Mar 26, 2021
bors merge |
Canceled. |
bors merge |
github-actions
bot
added
the
ready-to-merge
All that is left is for bors to build and merge this PR. (Remember you need to say `bors r+`.)
label
Mar 26, 2021
bors bot
pushed a commit
that referenced
this pull request
Mar 26, 2021
This adds `complete_semilattice_Sup` and `complete_semilattice_Inf` above `complete_lattice`. This has not much effect, as in fact either implies `complete_lattice`. However it's useful at times to have these, when you can naturally define just one half of the structure at a time (e.g. the subobject lattice in a general category, where for `Sup` we need coproducts and images, while for the `Inf` we need wide pullbacks). There are many places in mathlib that currently use `complete_lattice_of_Inf`. It might be slightly nicer to instead construct a `complete_semilattice_Inf`, and then use the new `complete_lattice_of_complete_semilattice_Inf`, but I haven't done that here. Co-authored-by: Scott Morrison <scott.morrison@gmail.com>
Canceled. |
bors merge |
bors bot
pushed a commit
that referenced
this pull request
Mar 27, 2021
This adds `complete_semilattice_Sup` and `complete_semilattice_Inf` above `complete_lattice`. This has not much effect, as in fact either implies `complete_lattice`. However it's useful at times to have these, when you can naturally define just one half of the structure at a time (e.g. the subobject lattice in a general category, where for `Sup` we need coproducts and images, while for the `Inf` we need wide pullbacks). There are many places in mathlib that currently use `complete_lattice_of_Inf`. It might be slightly nicer to instead construct a `complete_semilattice_Inf`, and then use the new `complete_lattice_of_complete_semilattice_Inf`, but I haven't done that here. Co-authored-by: Scott Morrison <scott.morrison@gmail.com>
Pull request successfully merged into master. Build succeeded: |
bors
bot
changed the title
feat(order/lattice): add complete_semilattice_Sup/Inf
[Merged by Bors] - feat(order/lattice): add complete_semilattice_Sup/Inf
Mar 27, 2021
b-mehta
pushed a commit
that referenced
this pull request
Apr 2, 2021
This adds `complete_semilattice_Sup` and `complete_semilattice_Inf` above `complete_lattice`. This has not much effect, as in fact either implies `complete_lattice`. However it's useful at times to have these, when you can naturally define just one half of the structure at a time (e.g. the subobject lattice in a general category, where for `Sup` we need coproducts and images, while for the `Inf` we need wide pullbacks). There are many places in mathlib that currently use `complete_lattice_of_Inf`. It might be slightly nicer to instead construct a `complete_semilattice_Inf`, and then use the new `complete_lattice_of_complete_semilattice_Inf`, but I haven't done that here. Co-authored-by: Scott Morrison <scott.morrison@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
delegated
The PR author may merge after reviewing final suggestions.
ready-to-merge
All that is left is for bors to build and merge this PR. (Remember you need to say `bors r+`.)
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds
complete_semilattice_Sup
andcomplete_semilattice_Inf
abovecomplete_lattice
.This has not much effect, as in fact either implies
complete_lattice
. However it's useful at times to have these, when you can naturally define just one half of the structure at a time (e.g. the subobject lattice in a general category, where forSup
we need coproducts and images, while for theInf
we need wide pullbacks).There are many places in mathlib that currently use
complete_lattice_of_Inf
. It might be slightly nicer to instead construct acomplete_semilattice_Inf
, and then use the newcomplete_lattice_of_complete_semilattice_Inf
, but I haven't done that here.