-
Notifications
You must be signed in to change notification settings - Fork 451
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
Reduction of Decidable
instances very slow when using cases
tactic.
#2552
Comments
Perhaps it's sensible to have a (maybe mathlib-only) linter which warns the user if they are using certain tactics to build data - I suspect similar instances of this have been caused by mathport porting lean 3 Also, adding credit for @ericrbg who helped with the minimisation a lot. |
It is strange to me that this would be slow in the first place. Do we have an explanation for the performance issue here? |
This works around leanprover/lean4#2552 - fix found by @b-mehta. I changed the `Nat` instance where the issue was found, and some `List` instances in hope it fixes mysterious slowdowns with `Finset` decidability. Any more instances changed would probably be good.
With #2559:
The terms further down don't look very nice:
|
Decidable
instances very slow when using cases
tactic.Decidable
instances very slow when using cases
tactic.
This works around leanprover/lean4#2552 - fix found by @b-mehta. I changed the `Nat` instance where the issue was found, and some `List` instances in hope it fixes mysterious slowdowns with `Finset` decidability. Any more instances changed would probably be good.
It is easy to write
Decidable
instances which usecases
internally, which are then unusable in the kernel.This issue, or something quite close to it, has come up multiple times now.
Example below provided by @kbuzzard and @bmehta on zulip:
The text was updated successfully, but these errors were encountered: