expression: avoid unnecessary warnings/errors when folding constants in control expr (#19675) #19910
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 #19675 to release-4.0
What problem does this PR solve?
Issue Number: close #17725
following #19367, avoid unnecessary warnings/errors when folding constants in control expr.
Problem Summary:
What is changed and how it works?
Proposal: xxx
What's Changed:
the scalar
if
is wrong, to be corrected here,add
tryFoldCounter
to try fold constrants but not throw warnings/erros.correct the special handler for control expressions.
How it Works:
each branch of control expressions fold contrants whenever possible, but not throw uncessary warnings/errors. When folding the control expressions, it run the normal branches and return normally like evaluating scalar expressions. If a branch is not const, it will stop folding constrants.
Related changes
Check List
Tests
Release note