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: Earlier call-context based dispatch filtering #13983
base: main
Are you sure you want to change the base?
Conversation
919931a
to
570654d
Compare
| @@ -778,9 +780,13 @@ module MakeImplCommon<InputSig Lang> { | |||
| * `ctx`. | |||
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.
This qldoc needs an update - it's no longer correct now that you've shuffled the columns around.
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 thought it was still correct; what would you suggest updating it to?
af34678
to
066ec79
Compare
#11725 reveals the following bad join-orders when calculating flow in
and flow out
The bad join-orders happen because we first join with the full dispatch relation, only to afterwards filter away impossible call targets based on call contexts. This PR reorders the joins so we immediately filter away impossible call targets, when possible.