feat(speculation): standard composed speculator - #451
Open
behinddwalls wants to merge 1 commit into
Open
Conversation
This was referenced Jul 28, 2026
behinddwalls
marked this pull request as ready for review
July 28, 2026 20:03
sbalabanov
approved these changes
Jul 28, 2026
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 29, 2026 18:12
19ee301 to
8dcd084
Compare
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
2 times, most recently
from
July 29, 2026 22:31
e8a2e32 to
2d2d88b
Compare
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 29, 2026 22:41
2d2d88b to
75716e5
Compare
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 29, 2026 23:08
75716e5 to
3ab1bc3
Compare
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 29, 2026 23:18
3ab1bc3 to
63e838f
Compare
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 29, 2026 23:18
63e838f to
3ea3843
Compare
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 30, 2026 01:19
3ea3843 to
a6cdd82
Compare
Add submitqueue/extension/speculation/speculator/standard, the standard Speculator. It funds the queue's most promising speculation paths first until the build budget is spent: candidates are considered in descending likelihood, in-flight paths stay funded rather than restarting, finished paths are never re-proposed, and everything below the budget cut waits for a later run. Where the ranking and the budget policy come from is swappable — the Generator ranks, the Allocator spends — so pairing bestfirst with sticky yields the default speculation policy, and changing either behavior means swapping a part, not writing a new Speculator. standard adds no cancellation handling of its own and inherits it from the two parts; a test pins that a cancelled run yields the context error and no actions. standard's behavior is documented next to the code in standard/README.md; the speculator README keeps only the extension contract.
behinddwalls
force-pushed
the
preetam/speculation-standard
branch
from
July 30, 2026 07:31
a6cdd82 to
3e1c931
Compare
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.
Add submitqueue/extension/speculation/speculator/standard, the standard Speculator. It funds the queue's most promising speculation paths first until the build budget is spent: candidates are considered in descending likelihood, in-flight paths stay funded rather than restarting, finished paths are never re-proposed, and everything below the budget cut waits for a later run. Where the ranking and the budget policy come from is swappable — the Generator ranks, the Allocator spends — so pairing bestfirst with sticky yields the default speculation policy, and changing either behavior means swapping a part, not writing a new Speculator.
standard adds no cancellation handling of its own and inherits it from the two parts; a test pins that a cancelled run yields the context error and no actions.
standard's behavior is documented next to the code in standard/README.md; the speculator README keeps only the extension contract.
Stack