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-500) Rename MultiMap.remove(K, V) to avoid clashes with newly introduced default methods in Java 8
Date Sun, 17 Nov 2013 17:11:20 GMT

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

Thomas Neidhart resolved COLLECTIONS-500.
-----------------------------------------

    Resolution: Fixed

Changed to boolean removeMapping(K, V) in r1542763.

> Rename MultiMap.remove(K, V) to avoid clashes with newly introduced default methods in
Java 8
> ---------------------------------------------------------------------------------------------
>
>                 Key: COLLECTIONS-500
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-500
>             Project: Commons Collections
>          Issue Type: Bug
>    Affects Versions: 4.0-alpha1
>            Reporter: Thomas Neidhart
>             Fix For: 4.0
>
>
> Java 8 will introduce new default methods for the Map interface which clash with the
existing method "V remove(K key, V value)" in our MultiMap interface.
> To avoid future problems rename the method to a more specific version and change the
return type to be more logical. Brief discussion on the ml favored either:
>  * boolean removeMapping(K key, V value)
>  * boolean removeValue(K key, V value)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message