-
Notifications
You must be signed in to change notification settings - Fork 274
Fix call stmt reporting #6191
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
base: master
Are you sure you want to change the base?
Fix call stmt reporting #6191
Conversation
This reverts commit 08f9846.
Co-authored-by: Alex Chew <[email protected]>
// This used to be 'a || OnlyFalse(a)' | ||
// but that stopped working for unknown reason |
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.
Does this need follow-up?
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.
I don't know. I don't understand the test generation well enough to know what is expected behavior. I'll ask @robin-aws to have a look, maybe he knows.
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.
Looks like the test generation is sensitive to token centers and has a few calls to the CallStmt
constructor for resolved statements that needed to be updated to preserve the old behavior. I've pushed a commit that fixes this test at least.
What was changed?
How has this been tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.