Class ImmutableCollection<E>
- java.lang.Object
- 
- java.util.AbstractCollection<E>
- 
- com.google.common.collect.ImmutableCollection<E>
 
 
- 
- All Implemented Interfaces:
- java.io.Serializable,- java.lang.Iterable<E>,- java.util.Collection<E>
 - Direct Known Subclasses:
- ImmutableList,- ImmutableMultiset,- ImmutableSet
 
 @DoNotMock("Use ImmutableList.of or another implementation") @GwtCompatible(emulated=true) public abstract class ImmutableCollection<E> extends java.util.AbstractCollection<E> implements java.io.Serializable ACollectionwhose contents will never change, and which offers a few additional guarantees detailed below.Warning: avoid direct usage of ImmutableCollectionas a type (just as withCollectionitself). Prefer subtypes such asImmutableSetorImmutableList, which have well-definedObject.equals(java.lang.Object)semantics, thus avoiding a common source of bugs and confusion.About allImmutable-collectionsThe remainder of this documentation applies to every public Immutable-type in this package, whether it is a subtype ofImmutableCollectionor not.GuaranteesEach makes the following guarantees: - Shallow immutability. Elements can never be added, removed or replaced in this
       collection. This is a stronger guarantee than that of Collections.unmodifiableCollection(java.util.Collection<? extends T>), whose contents change whenever the wrapped collection is modified.
- Null-hostility. This collection will never contain a null element.
- Deterministic iteration. The iteration order is always well-defined, depending on
       how the collection was created. Typically this is insertion order unless an explicit
       ordering is otherwise specified (e.g. ImmutableSortedSet.naturalOrder()). See the appropriate factory method for details. View collections such asImmutableMultiset.elementSet()iterate in the same order as the parent, except as noted.
- Thread safety. It is safe to access this collection concurrently from multiple threads.
- Integrity. This type cannot be subclassed outside this package (which would allow these guarantees to be violated).
 "Interfaces", not implementationsThese are classes instead of interfaces to prevent external subtyping, but should be thought of as interfaces in every important sense. Each public class such as ImmutableSetis a type offering meaningful behavioral guarantees. This is substantially different from the case of (say)HashSet, which is an implementation, with semantics that were largely defined by its supertype.For field types and method return types, you should generally use the immutable type (such as ImmutableList) instead of the general collection interface type (such asList). This communicates to your callers all of the semantic guarantees listed above, which is almost always very useful information.On the other hand, a parameter type of ImmutableListis generally a nuisance to callers. Instead, acceptIterableand have your method or constructor body pass it to the appropriatecopyOfmethod itself.Expressing the immutability guarantee directly in the type that user code references is a powerful advantage. Although Java offers certain immutable collection factory methods, such as Collections.singleton(Object)andSet.of, we recommend using these classes instead for this reason (as well as for consistency).CreationExcept for logically "abstract" types like ImmutableCollectionitself, eachImmutabletype provides the static operations you need to obtain instances of that type. These usually include:- Static methods named of, accepting an explicit list of elements or entries.
- Static methods named copyOf(orcopyOfSorted), accepting an existing collection whose contents should be copied.
- A static nested Builderclass which can be used to populate a new immutable instance.
 Warnings- Warning: as with any collection, it is almost always a bad idea to modify an element
       (in a way that affects its Object.equals(java.lang.Object)behavior) while it is contained in a collection. Undefined behavior and bugs will result. It's generally best to avoid using mutable objects as elements at all, as many users may expect your "immutable" object to be deeply immutable.
 Performance notes- Implementations can be generally assumed to prioritize memory efficiency, then speed of access, and lastly speed of creation.
- The copyOfmethods will sometimes recognize that the actual copy operation is unnecessary; for example,copyOf(copyOf(anArrayList))should copy the data only once. This reduces the expense of habitually making defensive copies at API boundaries. However, the precise conditions for skipping the copy operation are undefined.
- Warning: a view collection such as ImmutableMap.keySetorImmutableList.subList(int, int)may retain a reference to the entire data set, preventing it from being garbage collected. If some of the data is no longer reachable through other means, this constitutes a memory leak. Pass the view collection to the appropriatecopyOfmethod to obtain a correctly-sized copy.
- The performance of using the associated Builderclass can be assumed to be no worse, and possibly better, than creating a mutable collection and copying it.
- Implementations generally do not cache hash codes. If your element or key type has a slow
       hashCodeimplementation, it should cache it itself.
 Example usageclass Foo { private static final ImmutableSet<String> RESERVED_CODES = ImmutableSet.of("AZ", "CQ", "ZX"); private final ImmutableSet<String> codes; public Foo(Iterable<String> codes) { this.codes = ImmutableSet.copyOf(codes); checkArgument(Collections.disjoint(this.codes, RESERVED_CODES)); } }See alsoSee the Guava User Guide article on immutable collections. - Since:
- 2.0
- See Also:
- Serialized Form
 
- 
- 
Nested Class SummaryNested Classes Modifier and Type Class Description static classImmutableCollection.Builder<E>Abstract base class for builders ofImmutableCollectiontypes.
 - 
Method SummaryAll Methods Instance Methods Abstract Methods Concrete Methods Deprecated Methods Modifier and Type Method Description booleanadd(E e)Deprecated.Unsupported operation.booleanaddAll(java.util.Collection<? extends E> newElements)Deprecated.Unsupported operation.ImmutableList<E>asList()Returns anImmutableListcontaining the same elements, in the same order, as this collection.voidclear()Deprecated.Unsupported operation.abstract booleancontains(java.lang.Object object)abstract UnmodifiableIterator<E>iterator()Returns an unmodifiable iterator across the elements in this collection.booleanremove(java.lang.Object object)Deprecated.Unsupported operation.booleanremoveAll(java.util.Collection<?> oldElements)Deprecated.Unsupported operation.booleanretainAll(java.util.Collection<?> elementsToKeep)Deprecated.Unsupported operation.java.util.Spliterator<E>spliterator()java.lang.Object[]toArray()<T extends @Nullable java.lang.Object>
 T[]toArray(T[] other)- 
Methods inherited from class java.lang.Objectclone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 
- 
 
- 
- 
- 
Method Detail- 
iteratorpublic abstract UnmodifiableIterator<E> iterator() Returns an unmodifiable iterator across the elements in this collection.
 - 
spliteratorpublic java.util.Spliterator<E> spliterator() 
 - 
toArraypublic final java.lang.Object[] toArray() 
 - 
toArray@CanIgnoreReturnValue public final <T extends @Nullable java.lang.Object> T[] toArray(T[] other) 
 - 
containspublic abstract boolean contains(@CheckForNull java.lang.Object object) 
 - 
add@CanIgnoreReturnValue @Deprecated public final boolean add(E e) Deprecated.Unsupported operation.Guaranteed to throw an exception and leave the collection unmodified.
 - 
remove@CanIgnoreReturnValue @Deprecated public final boolean remove(@CheckForNull java.lang.Object object) Deprecated.Unsupported operation.Guaranteed to throw an exception and leave the collection unmodified.
 - 
addAll@CanIgnoreReturnValue @Deprecated public final boolean addAll(java.util.Collection<? extends E> newElements) Deprecated.Unsupported operation.Guaranteed to throw an exception and leave the collection unmodified.
 - 
removeAll@CanIgnoreReturnValue @Deprecated public final boolean removeAll(java.util.Collection<?> oldElements) Deprecated.Unsupported operation.Guaranteed to throw an exception and leave the collection unmodified.
 - 
retainAll@CanIgnoreReturnValue @Deprecated public final boolean retainAll(java.util.Collection<?> elementsToKeep) Deprecated.Unsupported operation.Guaranteed to throw an exception and leave the collection unmodified.
 - 
clear@Deprecated public final void clear() Deprecated.Unsupported operation.Guaranteed to throw an exception and leave the collection unmodified.
 - 
asListpublic ImmutableList<E> asList() Returns anImmutableListcontaining the same elements, in the same order, as this collection.Performance note: in most cases this method can return quickly without actually copying anything. The exact circumstances under which the copy is performed are undefined and subject to change. - Since:
- 2.0
 
 
- 
 
-