fix: avoid destroying reuse potential in LCNF simp#12388
fix: avoid destroying reuse potential in LCNF simp#12388
Conversation
hargoniX
commented
Feb 9, 2026
- fix: LCNF casesOnCtor can only act if type correct
- fix: this PR makes LCNF simp more tame to not destroy reuse information
|
!bench |
|
Benchmark results for d476a31 against 5ba467d are in! @hargoniX
Large changes (1✅, 2🟥)
Medium changes (1🟥)
Small changes (1✅, 27🟥) Too many entries to display here. View the full report on radar instead. |
|
!bench |
d476a31 to
1c00ced
Compare
|
Benchmark results for 1c00ced against 5ba467d are in! @hargoniX
Large changes (1✅)
Medium changes (1🟥)
Small changes (1✅, 23🟥) Too many entries to display here. View the full report on radar instead. |
|
!bench |
|
Benchmark results for 1e87a54 against 5ba467d are in! @hargoniX
Large changes (2✅, 7🟥)
Medium changes (24🟥) Too many entries to display here. View the full report on radar instead. Small changes (8✅, 1877🟥) Too many entries to display here. View the full report on radar instead. |
|
Mathlib CI status (docs):
|
|
Reference manual CI status:
|
This PR provides a `LawfulForwardPatternModel` instance for string patterns, i.e., it proves correctness of the `dropPrefix?` and `startsWith` functions for string patterns. Note that this is "just" the correctness proof; there isn't a way to actually use it yet. API lemmas will follow.
1e87a54 to
8311242
Compare
|
!bench |
|
Benchmark results for 8311242 against d2c738c are in! @hargoniX
Large changes (2✅, 7🟥)
Medium changes (3✅, 28🟥) Too many entries to display here. View the full report on radar instead. Small changes (16✅, 1925🟥) Too many entries to display here. View the full report on radar instead. |