Scala Buggabot

Teo Klestrup Röijezon (teozkr) said: Running into this in a project of mine. It runs a block of statements, and replaces it with the REPL output. Using this triggers warnings...

@xeno-by said: Even something as simple as this triggers the decribed issue: ```scala import scala.reflect.macros.whitebox._ import scala.language.experimental.macros object Macros { def impl(c: Context)(x: c.Tree) = { import c.universe._ q"()" }...

@som-snytt said: Thanks for reopening. I was faked out that day because the warning is emitted on `{ 2 == 1 }` but not on ```scala { val x =...

Imported From: https://issues.scala-lang.org/browse/SI-9012?orig=1 Reporter: @jrudolph Affected Versions: 2.10.4, 2.11.4

@paulp said: That's quite interesting because bar(null) should NEVER call the Blub-defined method. And indeed if that's the only bar in existence, it doesn't compile at all. ```scala a.scala:10: error:...

Imported From: https://issues.scala-lang.org/browse/SI-143?orig=1 Reporter: @lexspoon

@dubochet said: By-name arguments are printed correctly in Scaladoc 2.

Imported From: https://issues.scala-lang.org/browse/SI-5304?orig=1 Reporter: @djspiewak Affected Versions: 2.10.0 See #4859

@lrytz said: Spec 5.4 says bq. The new `m$cls` constructor is evaluated not at the point of the object definition, but is instead evaluated the first time m is dereferenced...

@adriaanm said: companion objects may have side effects, caveat inliner