Skip to content

Fix/#659 lambdalift proxies #671

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 2 commits into from
Jun 19, 2015

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jun 19, 2015

Fixes #659. Review by @DarkDimius

odersky added 2 commits June 19, 2015 15:35
Even if an explicit outer accessor was a method, it got a TermRef as type.
If an inner class has proxy fields, we missed so far the assignment sfrom
the proxy parameters in the primary constructor of the class to the proxy
fields.

Test case tries several variations of this.
@DarkDimius
Copy link
Contributor

Otherwise LGTM

@odersky
Copy link
Contributor Author

odersky commented Jun 19, 2015

It's hard, for sort of the same reason why liveness criteria are harder than safety criteria. We'd have to check that for certain classes of symbols, initializing assignments are generated. Let's defer that.

odersky added a commit that referenced this pull request Jun 19, 2015
@odersky odersky merged commit ad6c4ad into scala:master Jun 19, 2015
@DarkDimius
Copy link
Contributor

It's hard, for sort of the same reason why liveness criteria are harder than safety criteria. We'd have to check that for certain classes of symbols, initializing assignments are generated. Let's defer that.

I was commenting on bbc584f, meaning checking that outer-accessors do not get TermRef as type

@allanrenucci allanrenucci deleted the fix/#659-lambdalift-proxies branch December 14, 2017 19:21
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