Skip to content

Specialization + lazy vals = boom #447

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.

Sign up for GitHub

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

Jump to bottom
Closed
DarkDimius opened this issue Mar 31, 2015 · 2 comments
Closed

Specialization + lazy vals = boom #447

DarkDimius opened this issue Mar 31, 2015 · 2 comments

Comments

@DarkDimius
Copy link
Contributor

For the future reference: lazyVals phase makes low-level assumptions about how fields are stored, as it gets their addresses using Unsafe.

For this info to be consistent, specialization needs to also duplicate companion modules of classes that have lazy vals.
@DarkDimius
Copy link
Contributor Author

The proposed way to solve this(after we have specialization) is to run lazy-vals after specialization.

@DarkDimius DarkDimius mentioned this issue May 8, 2015
Closed
@DarkDimius
Copy link
Contributor Author

Lazy vals already run after erasure, ie after specialization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DarkDimius