Skip to content

Fix #1146: Fix bug of ExpandSAMs with non-apply SAM methods. #1147

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 1 commit into from
Mar 7, 2016

Conversation

sjrd
Copy link
Member

@sjrd sjrd commented Mar 5, 2016

When expanding a SAM, ExpandSAMs always used the name apply for the generated forwarder, instead of the name of the method which is abstract in the SAM type. This commit fixes this issue.

@sjrd
Copy link
Member Author

sjrd commented Mar 5, 2016

Review by @odersky, as you have written most of ExpandSAMs in the first place.

@sjrd sjrd force-pushed the fix-non-jvm-sam-non-apply branch 3 times, most recently from b4aa178 to 4b10e2b Compare March 7, 2016 15:17
@sjrd
Copy link
Member Author

sjrd commented Mar 7, 2016

For future PR's, it's best to push them to staging first and then make the PR from there. That lets everyone else push further commits on a PR with minimum hassle.

Ah OK.

But the way it is is also fine, so I leave it up to you whether you want to change it.

Done.

When expanding a SAM, ExpandSAMs always used the name `apply` for
the generated forwarder, instead of the name of the method which
is abstract in the SAM type. This commit fixes this issue.
odersky added a commit that referenced this pull request Mar 7, 2016
Fix #1146: Fix bug of ExpandSAMs with non-apply SAM methods.
@odersky odersky merged commit e5c5948 into scala:master Mar 7, 2016
@sjrd sjrd deleted the fix-non-jvm-sam-non-apply branch March 7, 2016 15:59
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.

2 participants