We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now that people realize LOC is not a measure of productivity, they want to eliminate as much code as possible by marking it @elidable.
@elidable
The compiler should not crash and then possibly attempt something sensible.
import annotation._ class X { @elidable(100) def x() = 42 } @elidable(500) class Y { def y() = 17 } class Z { @elidable(500) val z = 17 } object Test extends App { Console println new X().x() Console println new Y().y() Console println new Z().z }
As reported http://stackoverflow.com/questions/28923437/scala-elidable-causes-compiler-to-crash
The text was updated successfully, but these errors were encountered:
Imported From: https://issues.scala-lang.org/browse/SI-9207?orig=1 Reporter: @som-snytt Affected Versions: 2.11.6 Duplicates #10068
Sorry, something went wrong.
@som-snytt said: I missed the chance to use the punning test name FürElide. That's punning on the Beethoven tune the kids play.
FürElide
@SethTisue said: "elide", isn't that what Joe Wilson shouted at Obama?
No branches or pull requests
Now that people realize LOC is not a measure of productivity, they want to eliminate as much code as possible by marking it
@elidable
.The compiler should not crash and then possibly attempt something sensible.
As reported http://stackoverflow.com/questions/28923437/scala-elidable-causes-compiler-to-crash
The text was updated successfully, but these errors were encountered: