-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[BUG] Invalid com.sun.source.tree.LiteralTree generated by lombok? #2695
[BUG] Invalid com.sun.source.tree.LiteralTree generated by lombok? #2695
Comments
Can confirm that this is broken, already identified the root cause and will provide a PR soon. I also don't get why the unreferenced interface is required, thats fascinating 😄 Btw you can also upload files to github, that base64 encode archive was a little bit strange 😄 |
Thanks for the extremely quick support! Sorry for the strange archive, I must have been a bit to focused on the lombok problem to realize that it could be as simple as drag and drop to add an attachment, I saw the Video support, and just didn't read the full line😄. |
Describe the bug
When lombok executes as an annotation processor it seems like it produces invalid code.
To Reproduce
At the end of the report, there is a command to extract source.tgz which contains a maven project which shows the problem.
The following sequence should fail:
But if we move the source the compilation will work:
Expected behavior
The expected behavior is that both cases above should work.
Version info (please complete the following information):
Additional context
I have not been able to create a smaller crashing example, I have no clue why the interface and derived types are needed, but I think the @Singular is the root for this problem as the build() method get a lot more complex when @Singular is added (and if I remove it, the problems go away).
I have investigated the crash in checkerframework and got a workaround running, but I get the feeling that this is really a lombok problem.
The workaround in checkerframework is:
With this patch added the failing build succeeds but outputs:
Why do I think this is a lombok problem?
For me it seems very strange that checker framework manage to get its hands on a LiteralTree instance which has the kind NULL_LITERAL, which value isn't (Void) null, but instead an (Integer) 0.
Command to extract source.tgz:
The text was updated successfully, but these errors were encountered: