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

Warn on confusing order of operations #9

Open
nhthn opened this issue Oct 12, 2022 · 0 comments
Open

Warn on confusing order of operations #9

nhthn opened this issue Oct 12, 2022 · 0 comments
Labels
linter feature Feature requests for the Linter

Comments

@nhthn
Copy link
Contributor

nhthn commented Oct 12, 2022

sclint should warn if it encounters a binary op that is a child node of another binary op. A possible exception is if both binary ops are the same and are either "*" or "+". I think requiring (3 + 4) + 5 over 3 + 4 + 5 is a bit much especially if e.g. mixing together signals in a SynthDef.

@lnihlen lnihlen added the linter feature Feature requests for the Linter label Oct 12, 2022
@nhthn nhthn changed the title Detect confusing order of operations Warn on confusing order of operations Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
linter feature Feature requests for the Linter
Projects
None yet
Development

No branches or pull requests

2 participants