diff options
author | Matthieu Sozeau <mattam@mattam.org> | 2017-04-05 23:17:56 +0200 |
---|---|---|
committer | Matthieu Sozeau <matthieu.sozeau@inria.fr> | 2018-06-15 11:58:56 +0200 |
commit | 8ab4f8f76958d2603858ad3e4073be61ad38d113 (patch) | |
tree | 562f52d70b92717acaf0916fd9c0f91cb4ac0d61 /dev | |
parent | 31e13998542941040343cb81787a1d7c865d5b65 (diff) |
evd: restrict_evar with candidates, can raise NoCandidatesLeft
When restricting an evar with candidates, raise an exception if this
restriction would leave the evar without candidates, i.e. unsolvable.
- evarutil: mark restricted evars as "cleared"
They would otherwise escape being catched by the [advance] function
of clenv, and result in dangling evars not being registered to the shelf.
- engine: restrict_evar marks it cleared, update the future goals
We make the new evar a future goal and remove the old one.
If we did nothing, [unshelve tac] would work correctly as it
uses [Proofview.advance] to find the shelved goals, going through
the cleared evar. But [Unshelve] would fail as it expects only
undefined evars on the shelf and throws away the defined ones.
Diffstat (limited to 'dev')
0 files changed, 0 insertions, 0 deletions