REPL eagerly evaluates lazy vals

[cswinter]

scala> lazy val a = { println("side effect"); 0 } 
side effect
a: Int = 0

What scalac/ammonite do:

scala> lazy val a = { println("side effect"); 0 }
a: Int = <lazy>

[kcsongor]

I think this is an improvement, rather than a regression.

To me it makes perfect sense that when REPL prints the result of an expression, it has to force its value. Printing feels like a bit of a hack. That being said, this still might be unintended behaviour

[Jasper-M]

If the REPL immediately forces lazy vals, then there is absolutely no use for lazy vals in the REPL.

[felixmulder]

New REPL doesn't do this :)