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
With this code:
@EqualsAndHashCode public class BugExample { int a; transient int b; public BugExample(int a, int b) { this.a = a; this.b = b; } }
the field b in fact does make a difference for .equals. The regression was introduced in version 1.16.22; 1.16.20 works as documented.
b
.equals
Minimal example with tests exposing the issue: https://github.com/emlun/lombok-1.16.22-regression
Probably related to #1772.
The text was updated successfully, but these errors were encountered:
I'd bet this has been fixed in 1.18, just can't see it in the changelog.
Sorry, something went wrong.
Sorry, yep, it's fixed in f241ef8 on master. Also duplicate of #1724.
I mean it's not fixed in the 1.18.0 release, but I guess the fix will be included in the next release.
Work around @EqualsAndHashCode bug in Lombok 1.18.0
65dbc92
See projectlombok/lombok#1773
No branches or pull requests
With this code:
the field
b
in fact does make a difference for.equals
. The regression was introduced in version 1.16.22; 1.16.20 works as documented.Minimal example with tests exposing the issue: https://github.com/emlun/lombok-1.16.22-regression
Probably related to #1772.
The text was updated successfully, but these errors were encountered: