-
Notifications
You must be signed in to change notification settings - Fork 90
NPE when a value class is assigned to a val inside async block #83
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
Comments
Can you please try to reproduce this outside of the Scala worksheet to rule out that as a contributing factor? I can't reproduce it myself. |
Yes, I first hit the problem in my application code, then I screwed up trying to make a minimal repro. I updated the bug report, this now breaks in the REPL and as a compiled file. |
What version of Scala-async and Scala are you using? |
Scala 2.11.1, scala-async 0.9.1 |
I had trouble reproducing it because it was already fixed in the snapshot version (both for 2.10 and 2.11). I've just committed a test case to back this up, and will release a new version of async tomorrow. |
Great, thanks. |
I've just deployed scala-async 0.9.2 to Sonatype. |
See: #91 |
It appears that if you use a value class inside an async block, the async macro will throw a NullPointerException while it's trying to initialize the state machine. When I run this code:
I get this error:
The text was updated successfully, but these errors were encountered: