You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Stephen Kestle (JIRA)" <ji...@apache.org> on 2008/04/02 05:51:24 UTC

[jira] Created: (COLLECTIONS-293) EqualPredicate should be able to accept an Equator

EqualPredicate should be able to accept an Equator
--------------------------------------------------

                 Key: COLLECTIONS-293
                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-293
             Project: Commons Collections
          Issue Type: Improvement
          Components: Functor
            Reporter: Stephen Kestle
             Fix For: Generics


Currently the EqualPredicate checks according to Object.equals() but with [COLLECTIONS-252|the addition of the Equator interface], it can be made more powerful.

This will in turn make CollectionUtils.find() and select() more powerful as replacement methods for Collection.contains().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COLLECTIONS-293) EqualPredicate should be able to accept an Equator

Posted by "Stephen Kestle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COLLECTIONS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Kestle updated COLLECTIONS-293:
---------------------------------------

    Remaining Estimate: 2h
     Original Estimate: 2h

This depends on EqualPredicate being generified as in [COLLECTIONS-253]

> EqualPredicate should be able to accept an Equator
> --------------------------------------------------
>
>                 Key: COLLECTIONS-293
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-293
>             Project: Commons Collections
>          Issue Type: Improvement
>          Components: Functor
>            Reporter: Stephen Kestle
>            Assignee: Stephen Kestle
>             Fix For: Generics
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Currently the EqualPredicate checks according to Object.equals() but with [COLLECTIONS-252|the addition of the Equator interface], it can be made more powerful.
> This will in turn make CollectionUtils.find() and select() more powerful as replacement methods for Collection.contains().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (COLLECTIONS-293) EqualPredicate should be able to accept an Equator

Posted by "Stephen Kestle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COLLECTIONS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Kestle updated COLLECTIONS-293:
---------------------------------------

    Description: 
Currently the EqualPredicate checks according to Object.equals() but with the addition of the Equator interface in COLLECTIONS-252, it can be made more powerful.

This will in turn make CollectionUtils.find() and select() more powerful as replacement methods for Collection.contains().

  was:
Currently the EqualPredicate checks according to Object.equals() but with [COLLECTIONS-252|the addition of the Equator interface], it can be made more powerful.

This will in turn make CollectionUtils.find() and select() more powerful as replacement methods for Collection.contains().


> EqualPredicate should be able to accept an Equator
> --------------------------------------------------
>
>                 Key: COLLECTIONS-293
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-293
>             Project: Commons Collections
>          Issue Type: Improvement
>          Components: Functor
>            Reporter: Stephen Kestle
>            Assignee: Stephen Kestle
>             Fix For: Generics
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Currently the EqualPredicate checks according to Object.equals() but with the addition of the Equator interface in COLLECTIONS-252, it can be made more powerful.
> This will in turn make CollectionUtils.find() and select() more powerful as replacement methods for Collection.contains().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.