From 893585f526b852ff5059d279e69927fab0d41d42 Mon Sep 17 00:00:00 2001 From: Reinier Zwitserloot Date: Mon, 10 Feb 2014 20:22:33 +0100 Subject: [i386] documentation update for Data/Value's behaviour in the face of existing constructors. --- website/features/Data.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'website/features/Data.html') diff --git a/website/features/Data.html b/website/features/Data.html index ad3aa892..4d6e5609 100644 --- a/website/features/Data.html +++ b/website/features/Data.html @@ -38,7 +38,7 @@

If the class already contains a method with the same name as any method that would normally be generated, that method is not generated, and no warning or error is emitted. For example, if you already have a method with signature void hashCode(int a, int b, int c), no int hashCode() - method will be generated, even though technically int hashCode() is an entirely different method. The same rule applies to the constructor, + method will be generated, even though technically int hashCode() is an entirely different method. The same rule applies to the constructor (any explicit constructor will prevent @Data from generating one), toString, equals, and all getters and setters.

@Data can handle generics parameters for fields just fine. In order to reduce the boilerplate when constructing objects for classes with -- cgit