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

Document expression evaluation order #248

Open
Havvy opened this Issue Feb 19, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@Havvy
Copy link
Collaborator

Havvy commented Feb 19, 2018

@Havvy Havvy added the New Content label Feb 19, 2018

@fweimer

This comment has been minimized.

Copy link

fweimer commented Feb 19, 2018

The referenced discussion is about evaluation order. Operator precedence is something different, it's about whether A ⊕ B ⊙ C is interpreted as (A ⊕ B) ⊙ C or A ⊕ (B ⊙ C). That difference applies independently of the order of evaluation of A, B, and C.

@Havvy Havvy changed the title Document operator precedence Document expression evaluation order Feb 19, 2018

@Havvy

This comment has been minimized.

Copy link
Collaborator Author

Havvy commented Feb 19, 2018

This is what opening issues at 1AM does. Title fixed. Operator precedence is already documented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.