Skip to content

Preserve both subtrees when merging mt_backedges - #474

Merged
timholy merged 1 commit into
masterfrom
teh/fix364
Sep 1, 2026
Merged

timholy merged 1 commit into
masterfrom
teh/fix364

Conversation

@timholy

@timholy timholy commented Sep 1, 2026

Copy link
Copy Markdown
Member

join_invalidations! keeps the node already present in list, so join_branches! must merge the incoming node into that one. Merging in the opposite direction discarded the incoming callers, so invalidation_trees omitted invalidations that consolidate=false reported.

In the :deleting consolidation loop, covered now resets per edge, and the edge is wrapped in a BackedgeMT vector to match join_invalidations!.

Fixes #364

Assisted-by: Claude Opus 5 noreply@anthropic.com

`join_invalidations!` keeps the node already present in `list`, so
`join_branches!` must merge the incoming node into that one. Merging in the
opposite direction discarded the incoming callers, so `invalidation_trees`
omitted invalidations that `consolidate=false` reported.

In the `:deleting` consolidation loop, `covered` now resets per edge, and the
edge is wrapped in a `BackedgeMT` vector to match `join_invalidations!`.

Fixes #364

Assisted-by: Claude Opus 5 <noreply@anthropic.com>
@timholy
timholy merged commit 5fdabdc into master Sep 1, 2026
12 of 15 checks passed
@timholy
timholy deleted the teh/fix364 branch September 1, 2026 12:58
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.

Failure to insert invalidations by invalidation_trees()

1 participant