-
Notifications
You must be signed in to change notification settings - Fork 53
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 let and comma is awkward #1472
Comments
@cyrus- how do you feel about just moving to obligate parentheses for tuples? would address multiple issues. |
Not sure how the error reporting will work when there aren't parens? There would still need to a parse... |
outside parens/brackets i would think they should behave like undefined infix operators currently do; highlit in red, parsed as multihole. i think this is possible implementation wise but i might be underthinking it |
(implementation wise i think a direct fix to this issue is also non-straightforward; i'm not actually sure this is a regression? this seems intrinsic to the way n-ary ops are currently handled) |
actually nm this is a regression... it also breaks case expressions (if you have a bare tuple in the scrutinee) |
The text was updated successfully, but these errors were encountered: