Add cross-channel invalidation support#2
Merged
Merged
Conversation
Add ChannelCascade for channel-to-channel invalidation rules with cycle rejection and precomputed transitive closure, plus CrossChannelEdges for sparse (key, channel) -> (key, channel) dependencies with forward and reverse indexing. Keep both types usable without InvalidationTracker so embedders can adopt and test the primitives independently.
Integrate channel cascades and cross-channel edges into tracker marking, including full closure for the built-in eager and lazy policies. Also add multi-channel draining, cross-channel reachability queries, and document the limits of custom policies when cross-channel follow-up is involved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 expands
invalidationwith cross-channel invalidation support.What Changed
ChannelCascadefor channel-to-channel invalidation rules.CrossChannelEdges for sparse cross-key, cross-channel dependencies.InvalidationTracker.InvalidationTracker.PropagationPolicyimplementations when cross-channel follow-up is involved.Notes
markandmark_withonly change behavior when cascades or cross-channel edges are configured.