Imported From: https://issues.scala-lang.org/browse/SI-5808?orig=1
Reporter: Scott Morrison (scott)
Affected Versions: 2.9.2, 2.10.0-M3

Scott Morrison (scott) said:
(Modified code sample, so the lazy vals are not in the App; hopefully clearer.)

Scott Morrison (scott) said:
As Viktor explains on [scala-user] https://groups.google.com/d/msg/scala-user/JDODbZp-c1k/3JdGUkkKoWEJ, this is 'user-error', until SUGGEST-11 is implemented.

Scott Morrison (scott) said:
Just an instance of the problem described by SUGGEST-11.

Julien Diener (julien-diener) said (edited on Jan 20, 2017 12:20:50 PM UTC):
I found the same bug, is it supposed to be solved?
The suggest linked above is closed

Note the bug can be synthesized with the following code example:

object o{
  lazy val a = 1
  lazy val b = (1 to 1).par.map( i => o.a + i )
}    
o.b // never ends

@som-snytt said:
SIP is at the SIP page but I'm not sure what the status is.

It would be nice for the issue tracker to track SIPs for easy linking, maybe as a dedicated "Type" (SIP) or "Status" (Sipped).

The behavior is "not a bug" (because it's a feature or implementation detail) but also not "won't fix"; it's "out of scope" for an ordinary issue.