Either all or none of equals/hashCode/canEqual should be generated #313

Closed
lombokissues opened this Issue Jul 14, 2015 · 3 comments

Projects

None yet

1 participant

@lombokissues
Collaborator

Migrated from Google Code (issue 240)

@lombokissues
Collaborator

👤 r.spilker   🕗 Jul 18, 2011 at 19:02 UTC

These 3 methods are all part of the same implementation, and it makes no sense to generate only half of the methods. Either all or none should be generated (and when using @ EqualsAndHashCode, if none are generated, a warning should be emitted).

The docs already state that this is how it works, but that's not actually how it works.

Present in: 0.10.0-RC1

@lombokissues
Collaborator

👤 r.spilker   🕗 Jul 18, 2011 at 19:14 UTC

Well, the docs were a bit vague so those have also been updated. Will be in 0.10.0-RC2

fixed in commit 83e2fb5

@lombokissues
Collaborator

End of migration

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