Skip to content

@volatile vals inside objects are broken. #549

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 May 8, 2015 · 3 comments
Closed

@volatile vals inside objects are broken. #549

DarkDimius opened this issue May 8, 2015 · 3 comments
Labels
itype:bug prio:low

Comments

@DarkDimius
Copy link
Contributor

They get runtime offset(memory pointer) from companion class, and then try to operate on instances of the module class.
This could lead to arbitrary behavior, including killing the VM.
@DarkDimius
Copy link
Contributor Author

Marking this low priority as it does not stop us from bootstrapping.
At some point I want to refactor lazy vals, and that would be a good moment to fix this.

@DarkDimius
Copy link
Contributor Author

#447 also has the very same problem, but for a different reason.

@DarkDimius DarkDimius mentioned this issue Jun 26, 2015
Closed
@DarkDimius
Copy link
Contributor Author

This is fixed as of #1226

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

No branches or pull requests
1 participant
@DarkDimius