Skip to content

Fix #3182: return correct signatures for extractors #3184

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 3 commits into from
Sep 27, 2017

Conversation

liufengyun
Copy link
Contributor

fix #3182: return correct signatures for extractors

@liufengyun liufengyun requested a review from smarter September 27, 2017 00:24
@liufengyun
Copy link
Contributor Author

liufengyun commented Sep 27, 2017

@smarter I've added one more test case and improved the signature method.

productSelectors(mt.resultType).take(argLen)
.map(_.info.asSeenFrom(mt.resultType, mt.resultType.classSymbol).widen)
}
val sig =
Copy link
Member

Choose a reason for hiding this comment

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

I think it would be nice to document the different cases handled here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's done now, documenting helps think it more thoroughly and fix some hidden bugs 👍

@liufengyun liufengyun merged commit b78c050 into scala:master Sep 27, 2017
@liufengyun liufengyun deleted the fix-3182 branch September 27, 2017 20:25
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.

Exhaustivity checking of extractors statically known to return Some
2 participants