-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Lazy vals initialisation can be retried after exception #4451
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
Do we really want to do this? Is this a documented/specified behavior of scalac? |
I don't know if it is documented but it is for sure relied upon: https://github.com/scala/scala/blob/02776afa797fdf320dfefbaeb4b70431ee085b25/test/junit/scala/collection/immutable/LazyListTest.scala#L71 |
I found this that says:
|
@DarkDimius Is it intentional that the Dotty implementation of lazy val does not allow re-initialization after an exception? |
The lazy val is retried if it is annotated |
Fix #4451: Set flag in the correct order
The text was updated successfully, but these errors were encountered: