/*
* Copyright © 2009 Reinier Zwitserloot and Roel Spilker.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
* THE SOFTWARE.
*/
package lombok;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
/**
* Generates implementations for the equals
and hashCode
methods inherited by all objects.
*
* If either method already exists, then @EqualsAndHashCode
will not generate that particular method.
* If they all exist, @EqualsAndHashCode
generates no methods, and emits a warning instead to highlight
* that its doing nothing at all. The parameter list and return type are not relevant when deciding to skip generation of
* a method; any method named hashCode
will make @EqualsAndHashCode
not generate that method,
* for example.
*
* All fields that are non-static and non-transient are used in the equality check and hashCode generation. You can exclude
* more fields by specifying them in the exclude
parameter.
*
* Normally, auto-generating hashCode
and equals
implementations in a subclass is a bad idea, as
* the superclass also defines fields, for which equality checks/hashcodes won't be auto-generated. Therefore, a warning
* is emitted when you try. Instead, you can set the callSuper
parameter to true which will call
* super.equals
and super.hashCode
. Doing this with java.lang.Object
as superclass is
* pointless, so, conversely, setting this flag when NOT extending something (other than Object) will also generate
* a warning. Be aware that not all implementations of equals
correctly handle being called from a subclass!
* Fortunately, lombok-generated equals
implementations do correctly handle it.
*
* Array fields are handled by way of {@link java.util.Arrays#deepEquals(Object[], Object[])} where necessary, as well
* as deepHashCode
. The downside is that arrays with circular references (arrays that contain themselves,
* possibly indirectly) results in calls to hashCode
and equals
throwing a
* {@link java.lang.StackOverflowError}. However, the implementations for java's own {@link java.util.ArrayList} suffer
* from the same flaw.
*/
@Target(ElementType.TYPE)
@Retention(RetentionPolicy.SOURCE)
public @interface EqualsAndHashCode {
/**
* Any fields listed here will not be taken into account in the generated
* equals
and hashCode
implementations.
*/
String[] exclude() default {};
/**
* Call on the superclass's implementations of equals
and hashCode
before calculating
* for the fields in this class.
* default: false
*/
boolean callSuper() default false;
}