New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spurious errors when compiling the Scala library, depending on the file order #5644
Comments
Imported From: https://issues.scala-lang.org/browse/SI-5644?orig=1
|
@paulp said: As long as one file is BoxesRunTime.java, the second can be all kinds of things and it will crash. And in either order; so it's not exactly an order-of-arguments bug, just something which is sensitive to the order things unroll. scalac src/library/scala/runtime/BoxesRunTime.java src/library/scala/collection/Iterator.scala |
@dragos said: |
@paulp said: trait Foo { def contains(elem: Any) = List(1) exists(_ == elem) } |
@gkossakowski said:
|
@paulp said: |
@paulp said: |
@paulp said: |
@gkossakowski said: |
@paulp said: |
@dragos said: |
@paulp said: |
@dragos said: |
@paulp said: |
@paulp said: |
The compiler crashes with the following error in the backend (an overloaded type reaches backend):
The error appears and goes away depending on the order in which files are compiled. I can reproduce it by compiling together everything under 'src/library', in the order listed in the attached file. Run it with
scalac -d /tmp @sources-lib
.Sorry I cannot narrow it down more than this, but I hope it's enough to get someone to look at it. It's a blocker for anyone trying to build the Scala library in the IDE (or it may not, depending on the order in which it happens to build those files).
The text was updated successfully, but these errors were encountered: