Skip to content

Fix #5794: eta-expansion triggered properly #5795

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
Jan 26, 2019

Conversation

biboudis
Copy link
Contributor

Previously eta-expansion was not triggered because the refined type-ness wasn't taken under-consideration in two places.

  • functionArity was prohibiting the necessary branch to be taken: solved after dropping the refinement
  • isNonDepFunctionType wasn't checking whether the prototype was a refined type (also renamed method)

@biboudis biboudis requested a review from smarter January 25, 2019 15:08
@biboudis biboudis added this to the 0.13 Tech Preview milestone Jan 25, 2019
@biboudis biboudis self-assigned this Jan 25, 2019
@smarter
Copy link
Member

smarter commented Jan 25, 2019

To make the git history easier to follow, please squash these two commits in one commit, and add the description in #5795 (comment) to the commit message.

Previously eta-expansion was not triggered because the refined type-ness wasn't taken under-consideration in two places.

- `functionArity` was prohibiting the necessary branch to be taken: solved after dropping the refinement
- `isNonDepFunctionType` wasn't checking whether the prototype was a refined type (also renamed method)
@smarter smarter merged commit afe1e88 into scala:master Jan 26, 2019
@allanrenucci allanrenucci deleted the fix-#5794 branch January 26, 2019 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants