commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COLLECTIONS-333) Generic versions of Transformed* classes
Date Wed, 06 Mar 2013 20:04:13 GMT

     [ https://issues.apache.org/jira/browse/COLLECTIONS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Neidhart resolved COLLECTIONS-333.
-----------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 4.0)
         Assignee:     (was: Stephen Kestle)

Not going to happen, as this will break the respective collection contract as already discussed
before.

If somebody really want to do things like this, its better to use the respective collection
class without generics at all.
                
> Generic versions of Transformed* classes
> ----------------------------------------
>
>                 Key: COLLECTIONS-333
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-333
>             Project: Commons Collections
>          Issue Type: Improvement
>          Components: Bag, Collection, List, Set
>    Affects Versions: 3.2
>         Environment: OS X
>            Reporter: Edwin Tellman
>            Priority: Minor
>
> The generic version of Transformer required the input and output types to be identical.
 This seemed to me to reduce the usefulness of transformed collections, as transforming one
type into another seems like it would be a fairly common operation.  I'm not sure how to fix
this, however, as it also doesn't seem feasible to have a generic TransformedCollection with
different input and output types that implements Collection<E>.  Anyway, this patch
de-generifies TransformedCollection, which also fixes some compilation problems.  Please disregard
this change if you disagree and have a better solution.
> Cloned from COLLECTIONS-243, where there is much Transformed* discussion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message