[ http://issues.apache.org/jira/browse/COLLECTIONS-218?page=comments#action_12422290 ] Stephen Kestle commented on COLLECTIONS-218: --------------------------------------------
Binary compatibility only matters if the type is Serializable right? Is there something I'm missing? If someone is Serializing a static class, then it's a bit up the wall IMO. It's not going to break any client code, as they won't bu using a void return type. Is this just a business policy? > CollectionUtils.select() does not return passed in collection > ------------------------------------------------------------- > > Key: COLLECTIONS-218 > URL: http://issues.apache.org/jira/browse/COLLECTIONS-218 > Project: Commons Collections > Issue Type: Improvement > Components: Core > Affects Versions: 3.2 > Reporter: Stephen Kestle > Assigned To: Stephen Colebourne > Attachments: CollectionUtils select return.patch > > > collect has the following methods: > Collection collect(Collection inputCollection, final Transformer transformer) > Collection collect(Collection inputCollection, final Transformer transformer, > final Collection outputCollection) > The first creates an ArrayList(), where the second takes an outputCollection > and, for convenience, returns it. > Select (and selectReject) currently the following methods: > Collection select(Collection inputCollection, Predicate predicate) > void select(Collection inputCollection, Predicate predicate, Collection > outputCollection) > I propose changing the bottom method to return the passed in > outputCollection. It would simplify calling code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
