Dataflow: Simplify the call-edge join in reverse through-flow. #18515
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Alternative to #18355.
For a summary edge
arg->par->ret->out
found in reverse flow with access pathsap
atarg
/par
andinnerReturnAp
atret
/out
it seems superfluous to includeinnerReturnAp
in the call-edgearg
-par
join. The added constraint is that a path exists betweenpar
andret
with those access paths, but when we joinflowThroughIntoCall
in reverse flow, then that exactly what we just established, so I don't think it adds much (if anything). Dropping the column avoids the need to materialize a combination of 3 access paths (ap
,innerReturnAp
, andreturnAp
) that can vary independently in degenerate cases.