Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix parsing calls #843

Merged
merged 2 commits into from
Jul 31, 2023
Merged

Fix parsing calls #843

merged 2 commits into from
Jul 31, 2023

Conversation

Kijewski
Copy link
Contributor

This change:

  • adds a cut when the leading ( was encountered, and
  • fixed the interaction between call expressions and boolean OR.

@djc
Copy link
Owner

djc commented Jul 31, 2023

This will need to be rebased now, hope it's not too painful!

@Kijewski
Copy link
Contributor Author

No problem at all. :)

This change:

* adds a cut when the leading `(` was encountered, and
* fixed the interaction between call expressions and boolean OR.
This change

* allows using empty arrays `[]` in expessions,
* adds a cut when the leading `[` was encountered, and
* fixes the interaction between arrays and boolean OR.

IMO the restriction that you couldn't use empty arrays is not needed.
The missing cut made error messages slictly worse if you forget to add
the closing `]`.

Filter expressions must not have white spaces before the pipe `|`. The
white space is used to tell a filter expressions, and `std::ops::Or`
apart.
@Kijewski Kijewski mentioned this pull request Jul 31, 2023
@djc djc merged commit 985eb89 into djc:main Jul 31, 2023
17 checks passed
@Kijewski Kijewski deleted the pr-call branch July 31, 2023 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants