Use `eauto` as default for `set_solver`.
The set_solver
tactic roughly calls set_unfold
and then performs naive_solver
. @jihgfee noticed that set_solver
(without tactic argument) calls naive_solver idtac
by default. This is somewhat strange since naive_solver
(without tactic argument) defaults to naive_solver eauto
.
Also @jihgfee found an example where set_solver by idtac
(the current default) is much slower than set_solver by eauto
.
So I am wondering what's the reason why set_solver
uses idtac
? Is that just some arbitrary legacy choice, or does it actually improve performance?
Merge request reports
Activity
@jung Could you run timing with this MR on the reverse dependencies so we can figure this out?
Timing results will appear at:
Edited by Ralf Jung@jihgfee ping, is it possible to have a minimized example?
added 8 commits
-
44b93de4...c25b43ed - 6 commits from branch
master
- b37cd70f - Use `eauto` as default for `set_solver`.
- 9091657c - CHANGELOG.
-
44b93de4...c25b43ed - 6 commits from branch
enabled an automatic merge when the pipeline for 9091657c succeeds
mentioned in commit 3a32d06d
mentioned in merge request !457 (merged)
mentioned in issue #179 (closed)