fix: Unary-test expression with null value #689
Merged
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.
Description
Align the behavior of unary-tests with a comparison to
null
. In both cases, the engine returnsnull
.For example, the evaluation of
< 3
withnull
as the input value returnsnull
. Same as the comparisonnull < 3
returnsnull
.Fixing the behavior in the parser by introducing a special case for simple-positive-unary-test (i.e. comparison with the input value).
Related issues
closes #679