You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gilles Sadowski (Jira)" <ji...@apache.org> on 2023/07/29 06:55:00 UTC
[jira] [Commented] (LANG-1704) ImmutablePair and ImmutableTriple not actually final as documented
[ https://issues.apache.org/jira/browse/LANG-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748789#comment-17748789 ]
Gilles Sadowski commented on LANG-1704:
---------------------------------------
{quote}[...] classes are no longer final, even though their javadocs claim that they are.
{quote}
I agree that the change performed in commit 940b79b59c7e3b6db1d7ff64ce3350ded1481e61 (with no associated JIRA page) should be reverted.
The constructors should be made "private".
> ImmutablePair and ImmutableTriple not actually final as documented
> ------------------------------------------------------------------
>
> Key: LANG-1704
> URL: https://issues.apache.org/jira/browse/LANG-1704
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.tuple.*
> Affects Versions: 3.13.0
> Reporter: Dan Ziemba
> Priority: Minor
>
> As of commons-lang3 3.13.0, the ImmutablePair and ImmutableTriple classes are no longer final, even though their javadocs claim that they are. This is a problem because you can now subclass those and, for example, make an effectively mutable object that could be passed to a method with a parameter of type ImmutablePair.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)