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] - chore(Order/Lattice): Resolve porting notes #11034

Closed
wants to merge 1 commit into from

Conversation

YaelDillies
Copy link
Collaborator

  • The dsimp issue has been resolved.
  • I knew that the lemmas provable by simp were provable by simp in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
  • ematch is not coming back (and was already completely unused for years in Lean 3).
  • Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to sup_ind. It's not expectable that this will ever change, neither is it necessary.
  • Dot notation on Function.update is still broken. This is the last remaining porting note.

Open in Gitpod

* The `dsimp` issue has been resolved.
* I knew that the lemmas provable by `simp` were provable by `simp` in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
* `ematch` is not coming back (and was already completely unused for years in Lean 3).
* Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to `sup_ind`. It's not expectable that this will ever change, neither is it necessary.
* Dot notation on `Function.update` is still broken. This is the last remaining porting note.
@YaelDillies YaelDillies added awaiting-review The author would like community review of the PR t-order Order theory labels Feb 28, 2024
@Ruben-VandeVelde
Copy link
Collaborator

maintainer merge

Copy link

🚀 Pull request has been placed on the maintainer queue by Ruben-VandeVelde.

@riccardobrasca
Copy link
Member

Thanks!

bors merge

@github-actions github-actions 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 Feb 28, 2024
mathlib-bors bot pushed a commit that referenced this pull request Feb 28, 2024
* The `dsimp` issue has been resolved.
* I knew that the lemmas provable by `simp` were provable by `simp` in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
* `ematch` is not coming back (and was already completely unused for years in Lean 3).
* Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to `sup_ind`. It's not expectable that this will ever change, neither is it necessary.
* Dot notation on `Function.update` is still broken. This is the last remaining porting note.
@mathlib-bors
Copy link
Contributor

mathlib-bors bot commented Feb 28, 2024

Pull request successfully merged into master.

Build succeeded:

@mathlib-bors mathlib-bors bot changed the title chore(Order/Lattice): Resolve porting notes [Merged by Bors] - chore(Order/Lattice): Resolve porting notes Feb 28, 2024
@mathlib-bors mathlib-bors bot closed this Feb 28, 2024
@mathlib-bors mathlib-bors bot deleted the lattice_porting_notes branch February 28, 2024 12:01
riccardobrasca pushed a commit that referenced this pull request Mar 1, 2024
* The `dsimp` issue has been resolved.
* I knew that the lemmas provable by `simp` were provable by `simp` in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
* `ematch` is not coming back (and was already completely unused for years in Lean 3).
* Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to `sup_ind`. It's not expectable that this will ever change, neither is it necessary.
* Dot notation on `Function.update` is still broken. This is the last remaining porting note.
kbuzzard pushed a commit that referenced this pull request Mar 12, 2024
* The `dsimp` issue has been resolved.
* I knew that the lemmas provable by `simp` were provable by `simp` in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
* `ematch` is not coming back (and was already completely unused for years in Lean 3).
* Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to `sup_ind`. It's not expectable that this will ever change, neither is it necessary.
* Dot notation on `Function.update` is still broken. This is the last remaining porting note.
dagurtomas pushed a commit that referenced this pull request Mar 22, 2024
* The `dsimp` issue has been resolved.
* I knew that the lemmas provable by `simp` were provable by `simp` in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
* `ematch` is not coming back (and was already completely unused for years in Lean 3).
* Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to `sup_ind`. It's not expectable that this will ever change, neither is it necessary.
* Dot notation on `Function.update` is still broken. This is the last remaining porting note.
Louddy pushed a commit that referenced this pull request Apr 15, 2024
* The `dsimp` issue has been resolved.
* I knew that the lemmas provable by `simp` were provable by `simp` in Lean 3, but the simp nf linter was more lax. Now there's definitely no need to tag them.
* `ematch` is not coming back (and was already completely unused for years in Lean 3).
* Unification has changed in Lean 4, so it's really unsurprising that we need to provide an extra argument to `sup_ind`. It's not expectable that this will ever change, neither is it necessary.
* Dot notation on `Function.update` is still broken. This is the last remaining porting note.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintainer-merge ready-to-merge This PR has been sent to bors. t-order Order theory
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants