GH-131498: Allow 'peek' variables to be modified #132506
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
iritkatriel
approved these changes
Apr 14, 2025
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.
This PR lifts the restriction on the modification of input and "peek" variables.
This restriction was supposed to help avoid reference leaks, but actually just makes it annoying and inefficient to change values on the stack.
Plus, we have a better way to detect leaks on the stack:
Py_STACKREF_DEBUG.Doing this allows us to clean up some code and, more importantly for TOS caching, turn some arrays back into scalars.
This PR modifies
SWAPand_MAKE_CALLARGS_A_TUPLEto demonstrate the simplification.We can make further simplifications, but I'll save those for an other PR for ease of review.