-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Precedence of transposition operator ' #15858
Comments
Theoretically, this would be a breaking change, although it's hard to imagine it affecting real code. |
Currently transposition has higher precedence than multiplication and addition, and that's probably a good thing: But range has lower precedence than both:
which I think is likely quite common. |
Seems like the easiest way to solve this is to make |
@TotalVerb, good point, we can't make @timholy, please no. |
I don't think there really a problem here. I was just wondering whether we could make this slightly more convenient without making anything more painful. I'm inclined to close this issue. But I am right that |
I think implicit multiplication (which binds quite strongly, but not as strong as exponentiation) is also missing from that table, along with probably many other common ones. All the unicode ones are missing too, but those can probably be left out. |
This doesn't seem to be solvable with transitive operator precedence. |
Though not terrible, this is a bit unfortunate:
I can't find a case where one could want to create a range from a transposed last element. OTC, creating a row-matrix from a range can sometimes be useful.
Maybe we could change this? Or would it break something else?
Also,
'
isn't listed in the table about operator precedence.The text was updated successfully, but these errors were encountered: