JEP-19 Evaluation of Pipe Expressions #292
Open
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.
Sub Expression
The specification for
sub-expression
outlines how it should behave in pseudocode:However, this is incorrect, as many compliance tests expect the result to be
null
when the left-hand-side evaluates tonull
.So, the real pseudocode shoud in fact be:
Pipe Expression
However, it seems intuitive for
pipe-expression
to behave as is specified by the pseudocode above.Which means that the evaluation should still happens if the left-hand-side is
null
.Summary
This PR introduces a new compliance test that outlines the following expression:
search ( `null` | [@], {} ) -> [ null ]
in the hope to standardize the exact behaviour of pipe expressions.