[mypyc] Avoid cyclic reference in nested functions#16268
Merged
Conversation
ilevkivskyi
approved these changes
Oct 17, 2023
Member
ilevkivskyi
left a comment
There was a problem hiding this comment.
Looks great! Just one suggestion for a test.
| return any( | ||
| has_nested_func_self_reference(builder, nested) | ||
| for nested in builder.encapsulating_funcs.get(fitem, []) | ||
| ) |
Member
There was a problem hiding this comment.
I think it may be worth testing mutually recursive functions, something involving:
def f():
def g():
h()
def h():
g()
return g, hor are we already testing this?
Collaborator
Author
There was a problem hiding this comment.
Yeah, we already have at least the test case testNestedFunctions2 in mypyc/test-data/run-functions.test (mutual_recursion).
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.
Mypyc used to always put nested functions into the environment object, which results
in cyclic references, since the function object contains a reference to the environment.
Now we only do this if the body of a nested function refers to a nested function (e.g.
due to a recursive call). This means that in the majority of cases we can avoid the
cyclic reference.
This speeds up self check by an impressive 7%. I'm not sure exactly why the impact
is so big, but spending less time in the cyclic garbage collector is probably a big part.