Skip to content

Tree.Data.ForwardRuleMatches: fix erasure of consumed matches#299

Merged
JLimperg merged 1 commit intomasterfrom
forward-merge
Dec 14, 2025
Merged

Tree.Data.ForwardRuleMatches: fix erasure of consumed matches#299
JLimperg merged 1 commit intomasterfrom
forward-merge

Conversation

@JLimperg
Copy link
Collaborator

The central function for updating forward rule matches had a bug that
led to consumed matches (those that we've already tried to apply,
successfully or unsuccessfully) not being removed. Hence, we would try
to apply the same matches potentially many times. This involves checking
whether a hypothesis of the resulting type already exists, which means
one defeq check for each hyp in the context.

The central function for updating forward rule matches had a bug that
led to consumed matches (those that we've already tried to apply,
successfully or unsuccessfully) not being removed. Hence, we would try
to apply the same matches potentially many times. This involves checking
whether a hypothesis of the resulting type already exists, which means
one defeq check for each hyp in the context.
@JLimperg JLimperg enabled auto-merge December 14, 2025 19:02
@JLimperg JLimperg added this pull request to the merge queue Dec 14, 2025
Merged via the queue into master with commit a430982 Dec 14, 2025
1 check passed
@JLimperg JLimperg deleted the forward-merge branch December 14, 2025 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant