You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Matt Benson (JIRA)" <ji...@apache.org> on 2008/03/19 05:50:24 UTC
[jira] Updated: (COLLECTIONS-165) Filtered Maps, Lists, and Sets
[ https://issues.apache.org/jira/browse/COLLECTIONS-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Benson updated COLLECTIONS-165:
------------------------------------
Fix Version/s: (was: 3.3)
3.4
Concerns have been raised about adding new classes to [collections]; the community will have to reach a consensus before this will happen. Bumping to 3.4.
> Filtered Maps, Lists, and Sets
> ------------------------------
>
> Key: COLLECTIONS-165
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-165
> Project: Commons Collections
> Issue Type: New Feature
> Components: List, Map, Set
> Affects Versions: 3.1
> Environment: Operating System: other
> Platform: Other
> Reporter: Venkatesh Prasad Ranganath
> Priority: Minor
> Fix For: 3.4
>
> Attachments: FilteredCollection.java, FilteredList.java, FilteredListIterator.java, FilteredMap.java, FilteredSet.java
>
>
> In the project I work I have found that it would be efficient (at a small cost
> of memory) to use filtered maps, lists, and sets instead of creating a new copy
> of the decorated entities that contains only the filtered elements.
> To begin with I have implemented a FilteredMap and plan to implement
> FilteredList and FilteredSet. I will post the code for these in a couple of
> days and it would be great if Collections library could accept these contributions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.