expression: deduce result type for multi-argument functions like IF wrongly in some cases (#11605)
#11621
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/run-all-tests |
sre-bot
added
component/expression
type/3.0 cherry-pick
type/bugfix
|
/run-unit-test |
qw4990
added
status/can-merge
|
/run-all-tests |
zz-jason
approved these changes
Aug 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
cherry-pick #11605 to release-3.0
What problem does this PR solve?
Fix #11594;
When we deduce the result type for a multi-argument function like
IF, we don't takesigned/unsignedflag into account now;What is changed and how it works?
If anyone of these input arguments is not unsigned, we set the result type to signed.
Check List
Tests