Skip to content

Fix #3930: Handle multiple type arguments in overloading resolution #3985

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
Feb 13, 2018

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Feb 12, 2018

The error message for the neg case is a bit weird, (it complains about an
ambiguity error), but improving it would require considerable complications,
which I don't think are worth it at the present time.

The error message for the neg case is a bit weird, (it complains about an
ambiguity error), but improving it would require considerable complications,
which I don't think are worth it at the present time.
@odersky odersky requested a review from liufengyun February 12, 2018 14:36
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

@liufengyun liufengyun merged commit be8c3ba into scala:master Feb 13, 2018
@liufengyun liufengyun deleted the fix-#3930 branch February 13, 2018 06: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.

2 participants