-
Notifications
You must be signed in to change notification settings - Fork 34
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
Rule: unification used for variable assignment #3
Comments
The tricky thing in both this issue and #4 will be to determine whether unification really is intended — i.e. other constructs are less effective / elegant. For starters, I don't think we'll need to be too comprehensive in this check but just try and catch the simpler cases of one var/value on either side. |
There is however a great number of cases where the default allow = false
f(x) = x
foo[x] = y { } EDIT: And we do that now. |
Closing in favor of #4, which will be remodeled to be "Unnecessary unification". |
Avoid
Prefer
Motivation: while there are a few valid cases for unification, the unification operator (
=
) should not be used for simple assignment. TBD — more comprehensive explanation.The text was updated successfully, but these errors were encountered: