Skip to content

Python: Hotfix LocalSourceNode #6351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

tausbn
Copy link
Contributor

@tausbn tausbn commented Jul 22, 2021

Incorporates the changes from #6344 and #6345 and updates the change note to say that the use of LocalSourceNode in type tracking is being deprecated.

tausbn and others added 3 commits July 22, 2021 13:10
Temporarily instates `TypeTrackingNode` as an alias of `LocalSourceNode`
as having it as a separate class lead to performance regressions.

In the hopes that this will be resolved in the near future, I have left
the current `TypeTrackingNode` implementation in situ, but hidden inside
a `FutureWork` private module.
... in a local scope. Or rather, remove these from the `hasLocalSource`
relation.

This prevents a quadratic blowup when the same global is mentioned
_a lot_ of times within a single function scope.
@tausbn tausbn requested a review from a team as a code owner July 22, 2021 13:13
@tausbn tausbn merged commit 08f480a into github:rc/3.2 Jul 22, 2021
@tausbn tausbn deleted the python-hotfix-localsourcenode-typetrackingnode branch July 22, 2021 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants