[Merged by Bors] - chore(Order/Hom/WithTopBot): use to_dual#37274
[Merged by Bors] - chore(Order/Hom/WithTopBot): use to_dual#37274JovanGerb wants to merge 2 commits intoleanprover-community:masterfrom
to_dual#37274Conversation
PR summary f92dcbb69bImport changes for modified filesNo significant changes to the import graph Import changes for all files
|
| Current number | Change | Type |
|---|---|---|
| 452 | -1 | porting notes |
| 7435 | -1 | backward.isDefEq |
Current commit 6783a2eb26
Reference commit f92dcbb69b
You can run this locally as
./scripts/reporting/technical-debt-metrics.sh pr_summary
- The
relativevalue is the weighted sum of the differences with weight given by the inverse of the current value of the statistic. - The
absolutevalue is therelativevalue divided by the total sum of the inverses of the current values (i.e. the weighted average of the differences).
Komyyy
left a comment
There was a problem hiding this comment.
Thank you for your contribution!
I carefully confirmed that all declarations are dualized correctly.
maintainer merge
For maintainers: What I confirmed
- All declarations are dualized correctly.
- Definitions related to
LatticeHomcould not be directly dualized easily asto_dualcannot handle extended structure constructorLatticeHom.mk. withTopCongrcould not be directly dualized easily ase.toEquivusesRelIso.toEquivand the order relations ofRelIsoare flipped. We can useEquivLike.toEquivinstead, but this is not robust because of type class ambiguity:EquivLike (α ≃o β) α βandEquivLike ((· ≤ ·) ≃r (· ≤ ·)) α β.
|
🚀 Pull request has been placed on the maintainer queue by Komyyy. |
|
!radar |
|
Benchmark results for 6783a2e against f92dcbb are in. There are no significant changes. @riccardobrasca Warning These warnings may indicate that the benchmark results are not directly comparable, for example due to changes in the runner configuration or hardware.
Small changes (1✅, 1🟥)
|
|
Thanks! bors merge |
Use `to_dual` on `WithBot`/`WithTop` morphism definitions. This removes one `backward.isDefEq.respectTransparency` option. Intentionally remove `simps!` from `LatticeHom.withTopWithBot` and `LatticeHom.withTop'`, instead putting `simp` on the equivalent manual lemma`.
|
Pull request successfully merged into master. Build succeeded: |
to_dualto_dual
Use `to_dual` on `WithBot`/`WithTop` morphism definitions. This removes one `backward.isDefEq.respectTransparency` option. Intentionally remove `simps!` from `LatticeHom.withTopWithBot` and `LatticeHom.withTop'`, instead putting `simp` on the equivalent manual lemma`.
Use `to_dual` on `WithBot`/`WithTop` morphism definitions. This removes one `backward.isDefEq.respectTransparency` option. Intentionally remove `simps!` from `LatticeHom.withTopWithBot` and `LatticeHom.withTop'`, instead putting `simp` on the equivalent manual lemma`.
Use
to_dualonWithBot/WithTopmorphism definitions. This removes onebackward.isDefEq.respectTransparencyoption.Intentionally remove
simps!fromLatticeHom.withTopWithBotandLatticeHom.withTop', instead puttingsimpon the equivalent manual lemma`.