Selectors lack precendence
Open
selectors
- Dominant language
- Python
- Stars
- 5.8k
- Forks
- 541
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 5
Description
Not sure if this is a bug or as intended and needing documentation: Selectors lack precedence.
The filter operators "not" and "and" currently lack precedence. So `not >Z and |Z` is interpreted as `not (>Z and |Z)` instead of `(not >Z) and |Z` like how Python, C++, and general arithmetic work. If that's as intended, explaining that order of operations in the docs would be very helpful. Didn't check precedence of `and` vs `or`.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.