-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Data flow: Guard against viableImplInCallContext
not being a subset of viableCallable
#10505
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
Data flow: Guard against viableImplInCallContext
not being a subset of viableCallable
#10505
Conversation
b2b8aa6
to
27c9986
Compare
27c9986
to
167ad27
Compare
… of`viableCallable`
167ad27
to
2334099
Compare
2334099
to
914c711
Compare
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.
Python/shared changes look reasonable to me. 👍
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.
Right, this was already an implicit consistency requirement, so making it more explicit LGTM.
Also, adding the filter to enforce it in DataFlowImplCommon
looks fairly free, so that seems like a reasonable belt-and-suspenders fix.
Merge commit: 8b424d1
Merge commit: 8b424d1
Merge commit: 8b424d1
Merge commit: 8b424d1
This PR adds a guard against, and consistency query for, cases where
callable = viableImplInCallContext(call, _)
does not implycallable = viableCallable(call)
.As it turned out, this revealed a bug in the C# implementation, which is also fixed on this PR.