perf: better isDefEq cache in the presence of metavariables #8883
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.
This PR fixes the problem that unification in the presence of metavariables is often exponentially slow. This comes up every now and then in mathlib, and could get worse as mathlib continues to grow. This is implemented by handling the
defEqTrans
cache more carefully: we keep the cache as long as no metavariables are assigned.To know when to invalidate the cache, we keep track of the number of assignments inside of a
MetavarContext
. We also store this number inCache.defEqTrans
, so if this number doesn't match the number in the currentMetavarContext
, we invalidate the cache. We also revert the transient cache incheckpointDefEq
when needed (instead of emptying it).Alternatively, to identify if the
MetavarContext
has progressed, it would be possible to define and usePersistentHashMap.size
to find the number of assignments in theMetavarContext
, but I didn't go for this option.For this to work, in unification we need to wrap a
checkpointDefEq
around each branch that is backtracked on if it returnsfalse
. This was already meant to be like this, but some of these checkpoints were missing. In particular the addition in line 1932 (checkpointDefEq (isDefEqProjDelta t s i)
) was needed to build mathlib. I added it in other places where I deemed this necessary.The test file shows some examples improved by this fix.
The mathilb speedup from the fix is:
build
lint
Only one proof in mathlib had to be fixed. That particular failure was a unification that I think should not have been expected to work, and the fix was just a small change.
Zulip#lean4 > Exponential blowup in unification with metavariables @ 💬