Repository navigation
Feat: chunked eval-breaker polling for range loops (#206) - #260
Merged
Merged
Conversation
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.
Closes #206
ForRange runs in chunks of TP_POLL_INTERVAL and polls once per chunk; while loops keep the per-iteration countdown; break crosses the chunk loop via a label. Tests: structure (red on develop: 1 failed, 7 passed), results vs CPython across chunk boundaries and near +-2^63, KeyboardInterrupt in a long range loop. Local 3.15t full suite: 1228 passed, 3 skipped.
Interleaved, 7 pairs, load 3.2 to 3.9 (not quiet): spectral-norm 51.7x branch vs 51.0x develop, fannkuch 21.2x vs 21.7x, within noise. Benchmark compiled set identical to develop (nbody compiles nothing on both: the existing two-list-parameter FT rule, #220).