fix: remove withoutRecover
from apply
elaboration
#5862
Merged
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.
The assumptions behind disabling error recovery for the
apply
tactic no longer seem to hold, since tactic combinators likefirst
themselves disable error recovery when it makes sense.This addresses part of #3831
Breaking change:
elabTermForApply
no longer useswithoutRecover
. Tactics usingelabTermForApply
should evaluate whether it makes sense to wrap it withwithoutRecover
, which is generally speaking when it's used to elaborate identifiers.