Fix(optimizer): don't propagate equality constraints from IF/CASE outwards #2396
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.
This PR adds support for a
prune
callback argument inwalk_in_scope
, similar to howwalk
works. It then leverages it to fix the bug demonstrated below:Before:
After:
One obvious improvement that can be made in a followup PR (I plan to do this soon) is to reduce conditional expressions such as
IF
andCASE
when the conditions are statically known to beTRUE
orFALSE
.