Repository navigation
perf: bound helper-map summary reduction - #70
Merged
Merged
Conversation
picatz
marked this pull request as ready for review
October 9, 2026 04:15
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.
Summary
This is performance-only. Labeled inherited nested-helper precision limitations remain unchanged; map-range helpers and alias expansion are outside this change. Complexity is scoped to already-built events, with explicit block accounting and no whole-analyzer linearity claim.
Validation
Allocation measurements
At 12 diamonds / 37 blocks, complete helper-summary allocation is 8,672 B / 62 allocs per query, versus 24,615,976 B / 73,644 allocs at the base. All three repetitions agree. SSA setup is excluded.
Isolated reduction including event indexing is a separate benchmark: legacy 24,613,664 B / 73,596 allocs versus finite 6,360 B / 14 allocs, also stable across three repetitions. Shared-host timings are not used as throughput/speedup evidence.
No release or tag.