-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Consider adding <op>==
or <op>:=
assignment operators with semantics closer to |=
's
#2708
Comments
Methinks Since these additions would be modeled after On the other hand, the absence of these operators for so many years doesn't seem to have caused anyone much grief, whereas their addition would tend to make programs more difficult to decipher. (Most of whatever grief there has been, I believe, has been the result of bugs and/or inadequate or problematic documentation.) |
Yes, I also don't think those operators would be very useful. |
Excellent discussion. I'm going to close this now, but others should feel free to add their own two cents. |
See #1508, #2410.
We can't break backwards-compatibility and interoperability with gojq and jaq and others, but we could add new assignment operators.
The text was updated successfully, but these errors were encountered: