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.

Sign up for GitHub

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

Jump to bottom

[REFACTORING] Operator Grammar / Implementation #522

Open

rhazn opened this issue Feb 8, 2024 · 0 comments

Contributor

rhazn commented Feb 8, 2024

refactor this grammar to be more clearly readable (e.g. move all binary / ternary expressions into one type, have an easy and clear way to define order of execution instead of this weird setup of referring to the next lower expression)
add tests
refactor implementation to be less verbose / easier to read / less copy and paste between binary and ternary operators

See discussion in #521

rhazn mentioned this issue

Operator tests #526

Merged

georg-schwarz changed the title ~~Refactor operator Grammar / Implementation~~ [REFACTORING] Operator Grammar / Implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment