CPP: Prevent forced bad join order which is saved by context. #18828
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.
It is impossible to avoid a CP in this predicate on it's own.
Picking
getClassAndName
first is always a CP as it doesn't usenameWithoutArgs
. This disjunct cannot be picked asnot method instanceof ConversionOperator
requiresmethod
to be bound first.In practice the argument
result
also happens to be bound at the call site, sogetClassAndName
is not a CP at the call site. However the call site has no idea that we needmethod
to be bound and we join order assuming that it isn't so it. We also assume it isn't bound internally. This means that the join order is quite sensitive.An alternative would be to add
result
to the binding set to get a similar effect to what we do now (I wasn't sure whether to make this do what seems to be intended or whether to preserve the existing join order).