-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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
gh-126835: Move constant subscript folding to CFG #129568
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to wait until #129379 gets merged.
No, we can merge this first so you can make progress with the folding business. I'm still working on that one. |
Co-authored-by: Irit Katriel <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'll wait until the test case is split (#129568 (comment)) and then merge it. However, I think it's worth adding a NEWS entry as all our PRs related to moving the folding optimization from ast to CFG will require it.
Moving folding from ast construction to codegen/flowgraph definitely needs a news entry because ast.parse() is in the stdlib. Moving a folding from codegen to flow graph is no that exposed to users, but we might as well mention it in the whatsnew in case behaviour changed in some edge case and someone will want to look up why it may be so. That said, one whatnew entry about all the folding moves will probably be enough (pointing to multiple issues if need be). |
Agreed. So let's do it when all the folding has been moved. |
I have split tests and added |
|
|
|
|
|
|
|
@WolframAlph @Eclips4: This change introduced a reference leak, see #129635. |
cc @Eclips4 @tomasr8