Experiment: speed up decideFin! by optimizing terms #477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not merge (yet).
This is an experiment if we can make kernel reduction of the
Fin
counterexamples faster if we optimize the terms for kernel reduction, removing all overhead due to type classes andFin
.Before:
After:
Probably due to many many fast computations where just running it is faster
than optimizing it this way.
(The proofs therein are not very elegant, but I just wanted them done past 11pm…)