Skip to content

Leave arguments of infix operations tupled. #9159

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

Merged
merged 2 commits into from
Jun 22, 2020

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jun 11, 2020

Leave arguments of infix operations tupled in desugaring. Untuple them in typer
unless the function type is unary. This allows us to simply omit the operation in typer
when non-unary infix operations are removed.

Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Add" instead of "Added")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

odersky added 2 commits June 14, 2020 14:54
Leave arguments of infix operations tupled in desugaring. Untuple them in typer
unless the function type is unary. This allows us to simply omit the operation in typer
when auto tupling is disabled.
Untupling of infix operators is no longer under the noAutoTupling language feature.
Instead, we always untuple if the infix operator is not unary. The idea is that, going
forward we will gradually remove infix operators that are not unary. Once that is done
completely, and there are no more backwards compatibility concerbs, the code to untuple
arguments of infix operations will become dead code and can be removed.
Copy link
Contributor

@liufengyun liufengyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@odersky odersky merged commit f83943d into scala:master Jun 22, 2020
@odersky odersky deleted the change-infix-tuple branch June 22, 2020 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants