Correct wrong documentation regarding extensibility of ImmutablePair and ImmutableTriple. This closes #13 from github.

git-svn-id: https://svn.apache.org/repos/asf/commons/proper/lang/trunk@1592817 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Benedikt Ritter 2014-05-06 17:57:38 +00:00
parent bd7a8d5004
commit 01fe91839a
2 changed files with 4 additions and 4 deletions

View File

@ -21,8 +21,8 @@ package org.apache.commons.lang3.tuple;
*
* <p>Although the implementation is immutable, there is no restriction on the objects
* that may be stored. If mutable objects are stored in the pair, then the pair
* itself effectively becomes mutable. The class is also not {@code final}, so a subclass
* could add undesirable behaviour.</p>
* itself effectively becomes mutable. The class is also {@code final}, so a subclass
* can not add undesirable behaviour.</p>
*
* <p>#ThreadSafe# if both paired objects are thread-safe</p>
*

View File

@ -21,8 +21,8 @@ package org.apache.commons.lang3.tuple;
*
* <p>Although the implementation is immutable, there is no restriction on the objects
* that may be stored. If mutable objects are stored in the triple, then the triple
* itself effectively becomes mutable. The class is also not {@code final}, so a subclass
* could add undesirable behaviour.</p>
* itself effectively becomes mutable. The class is also {@code final}, so a subclass
* can not add undesirable behaviour.</p>
*
* <p>#ThreadSafe# if all three objects are thread-safe</p>
*