docs: roadmap — empirical findings from PR #18 attempt#19
Merged
Conversation
The validate_brackets fusion entry now references the closed PR #18, explains why the prototype showed no measurable improvement on the string-heavy multimodal bench (per-emit buf[pos] lookup cancels the savings from eliminating the second indices pass), and pins the revisit condition to a structurally-dense bench fixture appearing. Keeps the entry actionable: future contributors know the design has been tried, what failed, and what data to gather before retrying.
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
1 participant
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
Updates the `validate_brackets` fusion roadmap entry to reflect what we learned from attempting it in #18.
Before
The entry said "<1% effect on string-heavy workloads; worth revisiting only if profiling on structurally-dense input flags it" — accurate but didn't capture WHY a prototype attempt would have shown no gain.
After
Doc-only change. Keeps the roadmap actionable for future contributors.
Test plan