Repository navigation
Improvements to Heuristic Merger - #272
Merged
Merged
Conversation
garretrieger
commented
Oct 8, 2026
garretrieger
commented
Contributor
- Batching of inert segment merges
- Apply patch min/max's to all affected patches, not just exclusive ones.
- Better ordering when selecting candidate composite merges
All patches which do not intersect any frequency data have their sizes summed up and reported as a separate uncovered_ift_patch_cost line. This gives visibility into the size of the patches produced by the heuristic merger.
Don't perform merges which would grow a non-exclusive patch beyond the maximum.
…fig generated config.
First prefer merges that produce unitary/exclusive patches, then prefer merges with smaller number of segments, lastly break ties with segment set ordering.
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.