-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Bytecode generation bug involving magnolia and runtime annotations #19303
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
Comments
Another update on this. I said if both parameters to https://scastie.scala-lang.org/Xxt4t9sDTjWLV29eoB7btA
|
We need a minimization that does not have the |
I suppose we can dump the source code result of the call to |
You may try to write explicitly the expression that |
Hi, I have the same problem with Java annotations.
When result of this macro is used then full project with sbt run: https://github.com/xeppaka/macro-problem |
Uh oh!
There was an error while loading. Please reload this page.
Compiler version
3.3.1
Minimized code
Repro here
I'll copy/paste it in here anyway for convenience.
Output
Expectation
Should compile.
I don't have the time or knowledge to minimize away the magnolia dependency, I already extracted it from a big codebase.
I also don't know if the bug resides in magnolia or in the compiler. I'm filing it here because it's my best guess.
I'll explain the interesting thing I noticed while minimizing this. The error message refers to
Boolean
, which is actually a parameter to the@java.lang.Deprecated
annotation. If you remove the parameter I passed:the error message refers to
String
. if you provide both, the example compiles. The annotation seems to have to be retained at runtime to trigger this bug.Likely related: #15955
The text was updated successfully, but these errors were encountered: