Skip to content
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

scala-written ClassfileAnnotation argument name needs to be value #6082

Closed
scabug opened this issue Jul 14, 2012 · 4 comments
Closed

scala-written ClassfileAnnotation argument name needs to be value #6082

scabug opened this issue Jul 14, 2012 · 4 comments

Comments

@scabug
Copy link

scabug commented Jul 14, 2012

if one extends from ClassfileAnnotation, the compiler is confused about the argument name - it expects it to be value:

class annot(notValue: String) extends annotation.ClassfileAnnotation
@annot("") class C

gives

error: unknown annotation argument name: value
t5892.scala:2: error: annotation annot is missing argument notValue
@annot("") class C
 ^
@scabug
Copy link
Author

scabug commented Jul 14, 2012

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

@scabug
Copy link
Author

scabug commented Jan 13, 2013

@retronym said:
@lukas: is this what you had in mind?

retronym/scala@scala:2.10.x...retronym:ticket/6082

Or do you propose that we lift the "classfile annotation arguments must be named" restriction for Scala defined classfile annotations (which are pretty useless at the moment...)

@scabug
Copy link
Author

scabug commented Jan 14, 2013

@lrytz said:
I think that solution is what makes the most sense given the current situation. Thanks!

@scabug
Copy link
Author

scabug commented Jan 14, 2013

@retronym said:
scala/scala#1894

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants