Scala Buggabot

Imported From: https://issues.scala-lang.org/browse/SI-9714?orig=1 Reporter: @lrytz Affected Versions: 2.11.7

Imported From: https://issues.scala-lang.org/browse/SI-8440?orig=1 Reporter: @szeiger Affected Versions: 2.10.3

@retronym said: Null checking outer pointers before the call constructor, rather than inside it, would generate more bytecode. The stack trace does in include the real source of the error...

@szeiger said: I think there are 3 options to improve this, none of them without drawbacks: Either do the null check at the call site (more code), or add an...

Imported From: https://issues.scala-lang.org/browse/SI-10129?orig=1 Reporter: Tom Dyas (tdyas) Affected Versions: 2.11.8 Attachments: - [trace.txt](https://issues.scala-lang.org/secure/attachment/17325/trace.txt) (created on Jan 1, 2017 4:13:37 PM UTC, 16986 bytes)

Imported From: https://issues.scala-lang.org/browse/SI-4744?orig=1 Reporter: Christoph Breitkopf (bokesan) Affected Versions: 2.9.0, 2.11.2, 2.12.0-M5

@paulp said: That's nicely reduced. Given that the scala code compiles fine against the compiled java, there must be something we can do here.

@paulp said: https://github.com/scala/scala/pull/1422

Bhashit Parikh (bhashit) said (edited on May 31, 2014 3:19:46 PM UTC): I think this is still occurring when the java class in question is being referenced from any scala...

Dmytro Kondratiuk (dk14) said: Still experiencing issue with 2.11.2, 2.11.5 - http://stackoverflow.com/questions/28158173/building-a-project-with-mixed-scala-and-java-source-files-using-ant-illegal-cy