Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upScala compiler crash on 2.10 with Value Class, separate compilation. #6976
Comments
This comment has been minimized.
This comment has been minimized.
Imported From: https://issues.scala-lang.org/browse/SI-6976?orig=1
|
This comment has been minimized.
This comment has been minimized.
Artūras Šlajus (arturaz) said: Instead it seems that the bug is in implicit class handling logic in the compiler between compiles. On some projects even sbt clean does not help. Please take a look at attached implicits-bug.tar.bz2 file. |
This comment has been minimized.
This comment has been minimized.
Artūras Šlajus (arturaz) said: See ImplicitsBug.scala for step-by-step instructions on how to reproduce this. |
This comment has been minimized.
This comment has been minimized.
@retronym said: |
This comment has been minimized.
This comment has been minimized.
Artūras Šlajus (arturaz) said: |
This comment has been minimized.
This comment has been minimized.
@retronym said: |
This comment has been minimized.
This comment has been minimized.
@retronym said: |
This comment has been minimized.
This comment has been minimized.
@retronym said: |
This comment has been minimized.
This comment has been minimized.
Artūras Šlajus (arturaz) said: |
This comment has been minimized.
This comment has been minimized.
@retronym said: |
scabug commentedJan 15, 2013
Hello.
We're migrating from Play 2.0 & Scala 2.9.1 to Play 2.1 & Scala 2.10 and we have encountered a weird compiler error.
I think it's from this code:
The eqM is defined in trait Mocks which is mixed into the test class (using scalatest here).
The crash info is attached to the bug below.
My project configuration:
I'm not sure what else I can provide, but just ask if you need any more information.
Meanwhile - perhaps anyone can give me a hint what's happening and how to work around this?