Skip to content
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: Lattice closedness #7548

Closed
wants to merge 6 commits into from
Closed

Conversation

YaelDillies
Copy link
Collaborator

Define when a set in a lattice is closed under lattice operations.


Open in Gitpod

Define when a set in a lattice is closed under lattice operations.
Mathlib/Order/SupClosed.lean Outdated Show resolved Hide resolved
Mathlib/Order/SupClosed.lean Outdated Show resolved Hide resolved
Mathlib/Order/SupClosed.lean Outdated Show resolved Hide resolved
@YaelDillies YaelDillies added awaiting-review The author would like community review of the PR t-order Order hierarchy labels Oct 12, 2023

open Set

/-- A set `s` is *lattice-closed* if `a ⊔ b ∈ s` and `a ⊓ b ∈ s` for all `a ∈ s`, `b ∈ s`. -/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this also the name used in the literature? Or does this concept not exist in the mainstream literature?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This concept definitely exists in the literature: it's caled a sublattice. However I am trying to reserve this name for the bundled object, which I'm defining in #7549.

What do you think? Should I also say this is the property of being a sublattice? in the docstring or in the name?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would definitely mention this in the docstring. And I would even consider calling this isSublattice or something like that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess the argument for the current name is consistency with SupClosed and InfClosed.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've renamed it to IsSublattice for now.

Copy link
Member

@jcommelin jcommelin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks 🎉

bors merge

@leanprover-community-mathlib4-bot leanprover-community-mathlib4-bot added ready-to-merge This PR has been sent to bors. and removed awaiting-review The author would like community review of the PR labels Oct 26, 2023
bors bot pushed a commit that referenced this pull request Oct 26, 2023
Define when a set in a lattice is closed under lattice operations.
@bors
Copy link

bors bot commented Oct 26, 2023

Pull request successfully merged into master.

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot changed the title feat: Lattice closedness [Merged by Bors] - feat: Lattice closedness Oct 26, 2023
@bors bors bot closed this Oct 26, 2023
@bors bors bot deleted the lattice_closed branch October 26, 2023 11:12
grunweg pushed a commit that referenced this pull request Nov 1, 2023
Define when a set in a lattice is closed under lattice operations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has been sent to bors. t-order Order hierarchy
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

4 participants