Skip to content

Fix #3168: Don't insert apply if tree has method type #3198

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 4 commits into from
Sep 29, 2017

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Sep 27, 2017

It would be simply an eta-expansion followed by an application.
As #3168 shows, overloading resolution gets confused by this.

@allanrenucci
Copy link
Contributor

You mean #3168 not 3169

@odersky odersky changed the title Fix #3169: Don't insert apply if tree has method type Fix #3168: Don't insert apply if tree has method type Sep 27, 2017
@odersky
Copy link
Contributor Author

odersky commented Sep 27, 2017

Yes, indeed. #3168.

@allanrenucci
Copy link
Contributor

Your first commit message also refers to 3169 instead of 3168

@nicolasstucki
Copy link
Contributor

Needs rebase

It would be simply an eta-expansion followed by an application.
As scala#3168 shows, overloading resolution gets confused by this.
 - also rework previous test of scala#3189 to be a run test, just to make
   sure the problem is solved.
This one verifies that we still need the `isSyntheticApply` condition
in the test whether to elide an `apply` insertion attempt.
@odersky odersky merged commit 626ebf2 into scala:master Sep 29, 2017
@allanrenucci allanrenucci deleted the fix-#3168 branch December 14, 2017 19:18
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.

4 participants