fix: a recursor application is stuck if the major contains metavariables #4592
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.
(I will come back to this later)
Discrimination tree lookup throws an
isDefEqStuckEx
for any recursor application with metavariables. However, this should only be if there are metavariables in the major. I copied the same changes fromDiscrTree
toLazyDiscrTree
.This came up in a Zulip conversation. In particular, the
isDefEqStuck
exception happened intryUnificationHints
duringisDefEq
, which does aDiscrTree
lookup.