ivy: fix multi-frame variable lookup bug #81
Merged
Conversation
This file contains 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
robpike
requested changes
Dec 22, 2021
If g is calling f, f should never read or write g's variables. But that's what Lookup was doing: reading g's variables instead of globals of the same name. Assignment was correct. This change factors out the lookup to share it between both.
|
Fixed comment. |
robpike
approved these changes
Dec 23, 2021
|
Good catch. |
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.
If g is calling f, f should never read or write g's variables.
But that's what Lookup was doing: reading g's variables
instead of globals of the same name. Assignment was correct.
This change factors out the lookup to share it between both.