Fix parser bugs: underscore placeholder and spread pipe operator precedence #72
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.
Allow underscore '_' as a placeholder expression in function call arguments
(e.g.,
add(3, _)where_represents the piped value)Fix spread pipe operator precedence so that pipes inside function bodies
are correctly parsed when the function is a spread pipe operand
(e.g.,
list />>> (t) -> t.amount /> doublenow works correctly)Add inPipelineLiteral context flag to distinguish between pipeline
literal context (where pipes are stage separators) and regular expression
context (where pipes inside function bodies belong to the function)
Rename test variable 'flatten' to 'flattenLists' to avoid conflict with
builtin flatten function