SequencedCollection
interface.
The JDK does not provide any direct
implementations of this interface: it provides implementations of more
specific subinterfaces like Set
and List
. This interface
is typically used to pass collections around and manipulate them where
maximum generality is desired.
Bags or multisets (unordered collections that may contain duplicate elements) should implement this interface directly.
All general-purpose Collection
implementation classes (which
typically implement Collection
indirectly through one of its
subinterfaces) should provide two "standard" constructors: a void (no
arguments) constructor, which creates an empty collection, and a
constructor with a single argument of type Collection
, which
creates a new collection with the same elements as its argument. In
effect, the latter constructor allows the user to copy any collection,
producing an equivalent collection of the desired implementation type.
There is no way to enforce this convention (as interfaces cannot contain
constructors) but all of the general-purpose Collection
implementations in the Java platform libraries comply.
Certain methods are specified to be
optional. If a collection implementation doesn't implement a
particular operation, it should define the corresponding method to throw
UnsupportedOperationException
. Such methods are marked "optional
operation" in method specifications of the collections interfaces.
Some collection implementations
have restrictions on the elements that they may contain.
For example, some implementations prohibit null elements,
and some have restrictions on the types of their elements. Attempting to
add an ineligible element throws an unchecked exception, typically
NullPointerException
or ClassCastException
. Attempting
to query the presence of an ineligible element may throw an exception,
or it may simply return false; some implementations will exhibit the former
behavior and some will exhibit the latter. More generally, attempting an
operation on an ineligible element whose completion would not result in
the insertion of an ineligible element into the collection may throw an
exception or it may succeed, at the option of the implementation.
Such exceptions are marked as "optional" in the specification for this
interface.
It is up to each collection to determine its own synchronization policy. In the absence of a stronger guarantee by the implementation, undefined behavior may result from the invocation of any method on a collection that is being mutated by another thread; this includes direct invocations, passing the collection to a method that might perform invocations, and using an existing iterator to examine the collection.
Many methods in Collections Framework interfaces are defined in
terms of the equals
method. For example,
the specification for the contains(Object o)
method says: "returns true
if and only if this collection
contains at least one element e
such that
(o==null ? e==null : o.equals(e))
." This specification should
not be construed to imply that invoking Collection.contains
with a non-null argument o
will cause o.equals(e)
to be
invoked for any element e
. Implementations are free to implement
optimizations whereby the equals
invocation is avoided, for
example, by first comparing the hash codes of the two elements. (The
Object#hashCode()
specification guarantees that two objects with
unequal hash codes cannot be equal.) More generally, implementations of
the various Collections Framework interfaces are free to take advantage of
the specified behavior of underlying Object
methods wherever the
implementor deems it appropriate.
Some collection operations which perform recursive traversal of the
collection may fail with an exception for self-referential instances where
the collection directly or indirectly contains itself. This includes the
clone()
, equals()
, hashCode()
and toString()
methods. Implementations may optionally handle the self-referential scenario,
however most current implementations do not do so.
Most collections manage storage for elements they contain. By contrast, view
collections themselves do not store elements, but instead they rely on a
backing collection to store the actual elements. Operations that are not handled
by the view collection itself are delegated to the backing collection. Examples of
view collections include the wrapper collections returned by methods such as
Collections.
,
Collections.
, and
Collections.
.
Other examples of view collections include collections that provide a
different representation of the same elements, for example, as
provided by List.
,
NavigableSet.
,
Map.
, or
SequencedCollection.
.
Any changes made to the backing collection are visible in the view collection.
Correspondingly, any changes made to the view collection — if changes
are permitted — are written through to the backing collection.
Although they technically aren't collections, instances of
Iterator
and ListIterator
can also allow modifications
to be written through to the backing collection, and in some cases,
modifications to the backing collection will be visible to the Iterator
during iteration.
Certain methods of this interface are considered "destructive" and are called
"mutator" methods in that they modify the group of objects contained within
the collection on which they operate. They can be specified to throw
UnsupportedOperationException
if this collection implementation
does not support the operation. Such methods should (but are not required
to) throw an UnsupportedOperationException
if the invocation would
have no effect on the collection. For example, consider a collection that
does not support the add
operation. What will happen if the
addAll
method is invoked on this collection, with an empty
collection as the argument? The addition of zero elements has no effect,
so it is permissible for this collection simply to do nothing and not to throw
an exception. However, it is recommended that such cases throw an exception
unconditionally, as throwing only in certain cases can lead to
programming errors.
An unmodifiable collection is a collection, all of whose
mutator methods (as defined above) are specified to throw
UnsupportedOperationException
. Such a collection thus cannot be
modified by calling any methods on it. For a collection to be properly
unmodifiable, any view collections derived from it must also be unmodifiable.
For example, if a List is unmodifiable, the List returned by
List.
is also unmodifiable.
An unmodifiable collection is not necessarily immutable. If the
contained elements are mutable, the entire collection is clearly
mutable, even though it might be unmodifiable. For example, consider
two unmodifiable lists containing mutable elements. The result of calling
list1.equals(list2)
might differ from one call to the next if
the elements had been mutated, even though both lists are unmodifiable.
However, if an unmodifiable collection contains all immutable elements,
it can be considered effectively immutable.
An unmodifiable view collection is a collection that is unmodifiable
and that is also a view onto a backing collection. Its mutator methods throw
UnsupportedOperationException
, as described above, while
reading and querying methods are delegated to the backing collection.
The effect is to provide read-only access to the backing collection.
This is useful for a component to provide users with read access to
an internal collection, while preventing them from modifying such
collections unexpectedly. Examples of unmodifiable view collections
are those returned by the
Collections.
,
Collections.
, and
related methods.
Note that changes to the backing collection might still be possible, and if they occur, they are visible through the unmodifiable view. Thus, an unmodifiable view collection is not necessarily immutable. However, if the backing collection of an unmodifiable view is effectively immutable, or if the only reference to the backing collection is through an unmodifiable view, the view can be considered effectively immutable.
Serializability of collections is optional. As such, none of the collections
interfaces are declared to implement the java.
interface.
However, serializability is regarded as being generally useful, so most collection
implementations are serializable.
The collection implementations that are public classes (such as ArrayList
or HashMap
) are declared to implement the Serializable
interface if they
are in fact serializable. Some collections implementations are not public classes,
such as the unmodifiable collections. In such cases, the
serializability of such collections is described in the specification of the method
that creates them, or in some other suitable place. In cases where the serializability
of a collection is not specified, there is no guarantee about the serializability of such
collections. In particular, many view collections are not serializable,
even if the original collection is serializable.
A collection implementation that implements the Serializable
interface cannot
be guaranteed to be serializable. The reason is that in general, collections
contain elements of other types, and it is not possible to determine statically
whether instances of some element type are actually serializable. For example, consider
a serializable Collection<E>
, where E
does not implement the
Serializable
interface. The collection may be serializable, if it contains only
elements of some serializable subtype of E
, or if it is empty. Collections are
thus said to be conditionally serializable, as the serializability of the collection
as a whole depends on whether the collection itself is serializable and on whether all
contained elements are also serializable.
An additional case occurs with instances of SortedSet
and SortedMap
.
These collections can be created with a Comparator
that imposes an ordering on
the set elements or map keys. Such a collection is serializable only if the provided
Comparator
is also serializable.
This interface is a member of the Java Collections Framework.
Implementation Specification
The default method implementations (inherited or otherwise) do not apply any
synchronization protocol. If a Collection
implementation has a
specific synchronization protocol, then it must override default
implementations to apply that protocol.
Set
, List
, Map
, SortedSet
, SortedMap
, HashSet
, TreeSet
, ArrayList
, LinkedList
, Vector
, Collections
, Arrays
, AbstractCollection
Modifier and Type | Method and Description |
---|---|
public boolean | Returns: true if this collection changed as a result of the
callelement whose presence in this collection is to be ensured e)Ensures that this collection contains the specified element (optional operation). |
public boolean | Returns: true if this collection changed as a result of the callcollection containing elements to be added to this collection c)Adds all of the elements in the specified collection to this collection (optional operation). |
public void | |
public boolean | |
public boolean | Returns: true if this collection contains all of the elements
in the specified collectioncollection to be checked for containment in this collection c)Returns |
public boolean | |
public int | Returns: the hash code value for this collectionReturns the hash code value for this collection. |
public boolean | Returns: true if this collection contains no elementsReturns |
public Iterator | Returns: anIterator over the elements in this collectionRedeclares java. Returns an iterator over the elements in this collection. |
public default Stream | Returns: a possibly parallelStream over the elements in this
collectionReturns a possibly parallel |
public boolean | |
public boolean | Returns: true if this collection changed as a result of the
callcollection containing elements to be removed from this collection c)Removes all of this collection's elements that are also contained in the specified collection (optional operation). |
public default boolean | |
public boolean | Returns: true if this collection changed as a result of the callcollection containing elements to be retained in this collection c)Retains only the elements in this collection that are contained in the specified collection (optional operation). |
public int | Returns: the number of elements in this collectionReturns the number of elements in this collection. |
public default Spliterator | Returns: aSpliterator over the elements in this collectionOverrides default java. Creates a |
public default Stream | Returns: a sequentialStream over the elements in this collectionReturns a sequential |
public Object[] | Returns: an array, whose runtime component type isObject , containing all of the elements in this collectionReturns an array containing all of the elements in this collection. |
public < the component type of the array to contain the collection T> T[] | Returns: an array containing all of the elements in this collectionthe array into which the elements of this collection are to be
stored, if it is big enough; otherwise, a new array of the same
runtime type is allocated for this purpose. a)Returns an array containing all of the elements in this collection; the runtime type of the returned array is that of the specified array. |
public default < the component type of the array to contain the collection T> T[] | Returns: an array containing all of the elements in this collectiona function which produces a new array of the desired
type and the provided length generator)Returns an array containing all of the elements in this collection,
using the provided |
add | back to summary |
---|---|
public boolean add(E e) Ensures that this collection contains the specified element (optional
operation). Returns
Collections that support this operation may place limitations on what
elements may be added to this collection. In particular, some
collections will refuse to add
If a collection refuses to add a particular element for any reason
other than that it already contains the element, it must throw
an exception (rather than returning
|
addAll | back to summary |
---|---|
public boolean addAll(Collection<? extends E> c) Adds all of the elements in the specified collection to this collection (optional operation). The behavior of this operation is undefined if the specified collection is modified while the operation is in progress. (This implies that the behavior of this call is undefined if the specified collection is this collection, and this collection is nonempty.) If the specified collection has a defined encounter order, processing of its elements generally occurs in that order.
|
clear | back to summary |
---|---|
public void clear() Removes all of the elements from this collection (optional operation). The collection will be empty after this method returns.
|
contains | back to summary |
---|---|
public boolean contains(Object o) Returns
|
containsAll | back to summary |
---|---|
public boolean containsAll(Collection<?> c) Returns
|
equals | back to summary |
---|---|
public boolean equals(Object o) Compares the specified object with this collection for equality.
While the
The general contract for the
|
hashCode | back to summary |
---|---|
public int hashCode() Returns the hash code value for this collection. While the
|
isEmpty | back to summary |
---|---|
public boolean isEmpty() Returns
|
iterator | back to summary |
---|---|
public Iterator Redeclares java. Returns an iterator over the elements in this collection. There are no guarantees concerning the order in which the elements are returned (unless this collection is an instance of some class that provides a guarantee).
|
parallelStream | back to summary |
---|---|
public default Stream Returns a possibly parallel This method should be overridden when the Implementation Specification The default implementation creates a parallel
|
remove | back to summary |
---|---|
public boolean remove(Object o) Removes a single instance of the specified element from this
collection, if it is present (optional operation). More formally,
removes an element
|
removeAll | back to summary |
---|---|
public boolean removeAll(Collection<?> c) Removes all of this collection's elements that are also contained in the specified collection (optional operation). After this call returns, this collection will contain no elements in common with the specified collection.
|
removeIf | back to summary |
---|---|
public default boolean removeIf(Predicate<? super E> filter) Removes all of the elements of this collection that satisfy the given predicate (optional operation). Errors or runtime exceptions thrown during iteration or by the predicate are relayed to the caller. Implementation Specification The default implementation traverses all elements of the collection using
its
|
retainAll | back to summary |
---|---|
public boolean retainAll(Collection<?> c) Retains only the elements in this collection that are contained in the specified collection (optional operation). In other words, removes from this collection all of its elements that are not contained in the specified collection.
|
size | back to summary |
---|---|
public int size() Returns the number of elements in this collection. If this collection
contains more than
|
spliterator | back to summary |
---|---|
public default Spliterator Overrides default java. Creates a The default implementation should be overridden by subclasses that
can return a more efficient spliterator. In order to
preserve expected laziness behavior for the
These requirements ensure that streams produced by the
Implementation Specification The default implementation creates a
late-binding spliterator
from the collection's
The created Implementation Note The created If a spliterator covers no elements then the reporting of additional
characteristic values, beyond that of
|
stream | back to summary |
---|---|
public default Stream Returns a sequential This method should be overridden when the Implementation Specification The default implementation creates a sequential
|
toArray | back to summary |
---|---|
public Object[] toArray() Returns an array containing all of the elements in this collection.
If this collection makes any guarantees as to what order its elements
are returned by its iterator, this method must return the elements in
the same order. The returned array's runtime component type is The returned array will be "safe" in that no references to it are maintained by this collection. (In other words, this method must allocate a new array even if this collection is backed by an array). The caller is thus free to modify the returned array. API Note This method acts as a bridge between array-based and collection-based APIs.
It returns an array whose runtime type is
|
toArray | back to summary |
---|---|
public <T> T[] toArray(T[] a) Returns an array containing all of the elements in this collection; the runtime type of the returned array is that of the specified array. If the collection fits in the specified array, it is returned therein. Otherwise, a new array is allocated with the runtime type of the specified array and the size of this collection. If this collection fits in the specified array with room to spare
(i.e., the array has more elements than this collection), the element
in the array immediately following the end of the collection is set to
If this collection makes any guarantees as to what order its elements are returned by its iterator, this method must return the elements in the same order. API Note This method acts as a bridge between array-based and collection-based APIs.
It allows an existing array to be reused under certain circumstances.
Use Suppose String[] y = new String[SIZE]; ... y = x.toArray(y); The return value is reassigned to the variable Note that
|
toArray | back to summary |
---|---|
public default <T> T[] toArray(IntFunction<T[]> generator) Returns an array containing all of the elements in this collection,
using the provided If this collection makes any guarantees as to what order its elements are returned by its iterator, this method must return the elements in the same order. API Note This method acts as a bridge between array-based and collection-based APIs.
It allows creation of an array of a particular runtime type. Use
Suppose String[] y = x.toArray(String[]::new); Implementation Specification The default implementation calls the generator function with zero
and then passes the resulting array to
|