-
Notifications
You must be signed in to change notification settings - Fork 21
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
Scalala and @specialized don't get along with Scala 2.9.x #4541
Comments
Imported From: https://issues.scala-lang.org/browse/SI-4541?orig=1 |
Daniel Ramage (dramage) said: |
@dragos said: |
Daniel Ramage (dramage) said: |
Matthew Pocock (drdozer) said: |
@axel22 said (edited on Sep 28, 2011 4:38:33 PM UTC): |
Matthew Pocock (drdozer) said: |
@axel22 said:
|
=== What steps will reproduce the problem ===
Checkout Scalala from my repo at the following points.
Run: sbt update; sbt compile
Branch: https://github.com/retronym/Scalala/commits/scala-2.9-take2
https://github.com/retronym/Scalala/tree/b64ee3647f9654d83c58391644e1f6c8c54faacd
https://github.com/retronym/Scalala/tree/e32202b6c0ee925cbab4d943d5bcbedf37f7aa2d
=== What is the expected behavior? ===
Successful compilation, as per -no-specialization
=== What do you see instead? ===
Compilation failure.
=== Additional information ===
I haven't had time to isolate these yet. But I wanted to post a bug to make this issue visible in the lead up to 2.9.0.
=== What versions of the following are you using? ===
The text was updated successfully, but these errors were encountered: