summaryrefslogtreecommitdiffstats
path: root/ri/src/main/java/javax/annotation/concurrent/Immutable.java
diff options
context:
space:
mode:
Diffstat (limited to 'ri/src/main/java/javax/annotation/concurrent/Immutable.java')
-rw-r--r--ri/src/main/java/javax/annotation/concurrent/Immutable.java36
1 files changed, 0 insertions, 36 deletions
diff --git a/ri/src/main/java/javax/annotation/concurrent/Immutable.java b/ri/src/main/java/javax/annotation/concurrent/Immutable.java
deleted file mode 100644
index 03f1cb5..0000000
--- a/ri/src/main/java/javax/annotation/concurrent/Immutable.java
+++ /dev/null
@@ -1,36 +0,0 @@
-package javax.annotation.concurrent;
-
-import java.lang.annotation.Documented;
-import java.lang.annotation.ElementType;
-import java.lang.annotation.Retention;
-import java.lang.annotation.RetentionPolicy;
-import java.lang.annotation.Target;
-
-/*
- * Copyright (c) 2005 Brian Goetz
- * Released under the Creative Commons Attribution License
- * (http://creativecommons.org/licenses/by/2.5)
- * Official home: http://www.jcip.net
- */
-
-/**
- * Immutable
- *
- * The class to which this annotation is applied is immutable. This means that
- * its state cannot be seen to change by callers. Of necessity this means that
- * all public fields are final, and that all public final reference fields refer
- * to other immutable objects, and that methods do not publish references to any
- * internal state which is mutable by implementation even if not by design.
- * Immutable objects may still have internal mutable state for purposes of
- * performance optimization; some state variables may be lazily computed, so
- * long as they are computed from immutable state and that callers cannot tell
- * the difference.
- *
- * Immutable objects are inherently thread-safe; they may be passed between
- * threads or published without synchronization.
- */
-@Documented
-@Target(ElementType.TYPE)
-@Retention(RetentionPolicy.CLASS)
-public @interface Immutable {
-}