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
Cleanup the hypothesis conversion function #10052
Conversation
There are a couple of check: false you add to set. Is it intentional? |
Outside of |
I meant SSR, not set sorry I wrote with my phone. I will point them out |
It is when you call reduct_in_concl that I see false. Did you change its behaviour? |
As far as I can tell, |
Thanks, then this pr is good to me. |
@herbelin you've been touching this code recently, do you want to be the assignee of this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you want to be the assignee of this PR?
I can formally do the merge, but if someone had a closer look to the algorithmic part of the code than I had (@jashug or @gares), maybe can he also do the merge.
A side remark: What are the plans for logic.ml
, wasn't it the plan that it eventually disappears? If so, maybe can Logic.convert_hyp
goes to tactics.ml
directly?
I thought about that, but |
@herbelin Also, there is not much algorithmic change for now, this PR is mostly a matter of moving code around and writing stupid fast paths. |
I was thinking to the |
285c802
to
479a547
Compare
I assigned, but overlays are needed for the now mandatory |
@herbelin Yes, that was green, strangely enough. I'll write overlays anyways. |
479a547
to
685313f
Compare
685313f
to
ed99695
Compare
@herbelin should be ready modulo CI. |
OK, shall merge tomorrow if no objections by then. (The Ltac2 test should now be deactivated as far as I understood?) |
FTR, Ltac2 has been removed from the CI, so no problem anymore. |
This prevents having to call global functions, for no good reason. We also seize the opportunity to name the check argument.
The current situation is a mess, some functions set it by default, but other no. Making it mandatory ensures that the expected value is the correct one.
Doesn't seem to matter in practice, but it doesn't hurt either.
ed99695
to
1b4c0a1
Compare
This PR is an infrastructure change before the proper fix for #9919, and can be considered a followup of #9983.
The first commit alone, by only recomputing the order of named contexts after a change when the
check
flag is set is responsible for an important speed-up of Flocq.(N.B.: the coq-mathcomp-ssreflect apparent slowdown is noise, as hinted by the mostly unchanged cycle count. I had run another bench before rebasing where this did not happen.)
Overlays: