perf: increase prio of AddCommMonoid.toAddMonoid#39689
Conversation
|
!radar |
|
Benchmark results for a869a59 against c669471 are in. There are significant results. @kbuzzard
No significant changes detected. |
PR summary 63bdd3cb0bImport changes for modified filesNo significant changes to the import graph Import changes for all files
|
|
I once did an experiment where I increased all the priorities of CommX.toX and it went well. |
|
!radar |
|
Benchmark results for 9f4a236 against c669471 are in. There are significant results. @kbuzzard
No significant changes detected. |
|
!radar |
|
Benchmark results for a36a26e against c669471 are in. There are significant results. @kbuzzard
No significant changes detected. |
|
!radar (fingers crossed this time) |
|
Benchmark results for ee743b8 against c669471 are in. There are significant results. @kbuzzard
Large changes (1✅)
Medium changes (12✅, 1🟥)
Small changes (85✅, 29🟥) Too many entries to display here. View the full report on radar instead. |
|
At the suggestion of Matt Ballard, I might try groups/rings too. |
|
!radar |
|
Benchmark results for 63bdd3c against 2800ac2 are in. There are significant results. @kbuzzard
Large changes (1✅) 1 hidden Medium changes (21✅) Too many entries to display here. View the full report on radar instead. Small changes (102✅, 20🟥) Too many entries to display here. View the full report on radar instead. |
The idea is that to prove M is an additive monoid, then essentially always it's a good idea to try to prove that it's a commutative additive monoid. This is in stark contrast to multiplication, which is often not commutative.
This change will not make failures any slower, but it might make successes faster.