Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative high-level breakdown of patch extension algorithm #239

Open
skef opened this issue Nov 19, 2024 · 0 comments
Open

Alternative high-level breakdown of patch extension algorithm #239

skef opened this issue Nov 19, 2024 · 0 comments

Comments

@skef
Copy link
Contributor

skef commented Nov 19, 2024

We've already discussed changing the current description so that instead of creating a single list of patches, we create lists by invalidation status: full, partial, or no. When we discussed this the idea was to process them in that order. We've also discussed using the order of entries in the map for tie breaking, so we'll probably want to say that when the patches are broken out into these lists the ordering must be preserved.

In addition to that, I propose that we change the description to say that the list of full invalidation patches (if any) must be processed first. Then, once there are no remaining intersecting full invalidation patches, the remaining two lists can be processed concurrently. This makes the nature of partial invalidation patches clear in the algorithm and is better relative to the concerns of this thread.

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

No branches or pull requests

1 participant