On 11/14/2013 11:36 PM, Phil Steitz wrote:
> On 11/14/13 1:06 PM, Thomas Neidhart wrote:
>> On 11/14/2013 06:12 AM, Gary Gregory wrote:
>>> How about the name removeEntry|Entries since there is a Map.Entry.
>> Also possible, but there is a subtle difference imho:
>>
>> * removeMapping does not ass
On 11/15/2013 09:06 AM, Jörg Schaible wrote:
> Hi Thomas,
>
> Thomas Neidhart wrote:
>
>> Hi,
>>
>> during the vote for collections 4.0 we have discovered a problem wrt the
>> MultiMap interface in general and specifically the MultiKeyMap.
>>
>> Java 8 introduces a new default method in the Map i
Hi Thomas,
Thomas Neidhart wrote:
> Hi,
>
> during the vote for collections 4.0 we have discovered a problem wrt the
> MultiMap interface in general and specifically the MultiKeyMap.
>
> Java 8 introduces a new default method in the Map interface:
>
> boolean remove(Object key, Object value)
On 11/14/13 2:39 PM, Paul Benedict wrote:
> For anyone's observation, I sent this question to the Open JDK list because
> I am so surprised how adding default methods can break custom interface
> extensions. I was really hoping default methods would be much more subtle
> but it turns out this could
For anyone's observation, I sent this question to the Open JDK list because
I am so surprised how adding default methods can break custom interface
extensions. I was really hoping default methods would be much more subtle
but it turns out this could be a common occurrence going forward. What if
JDK
On 11/14/13 1:06 PM, Thomas Neidhart wrote:
> On 11/14/2013 06:12 AM, Gary Gregory wrote:
>> How about the name removeEntry|Entries since there is a Map.Entry.
> Also possible, but there is a subtle difference imho:
>
> * removeMapping does not assume that such a mapping exists, whereas
> * remov
On 11/14/2013 06:12 AM, Gary Gregory wrote:
> How about the name removeEntry|Entries since there is a Map.Entry.
Also possible, but there is a subtle difference imho:
* removeMapping does not assume that such a mapping exists, whereas
* removeEntry sounds like you remove an entry that you are s
How about the name removeEntry|Entries since there is a Map.Entry.
Gary
On Wed, Nov 13, 2013 at 4:49 PM, Thomas Neidhart
wrote:
> Hi,
>
> during the vote for collections 4.0 we have discovered a problem wrt the
> MultiMap interface in general and specifically the MultiKeyMap.
>
> Java 8 introdu
The thread is here:
http://mail.openjdk.java.net/pipermail/lambda-dev/2013-November/011397.html
On Wed, Nov 13, 2013 at 7:40 PM, Paul Benedict wrote:
> I will forward a portion of this email to the OpenJDK folks and see what
> they think about compatibility options.
>
>
> On Wed, Nov 13, 2013 a
I will forward a portion of this email to the OpenJDK folks and see what
they think about compatibility options.
On Wed, Nov 13, 2013 at 3:49 PM, Thomas Neidhart
wrote:
> Hi,
>
> during the vote for collections 4.0 we have discovered a problem wrt the
> MultiMap interface in general and specific
Hi,
during the vote for collections 4.0 we have discovered a problem wrt the
MultiMap interface in general and specifically the MultiKeyMap.
Java 8 introduces a new default method in the Map interface:
boolean remove(Object key, Object value)
This clashes with the method in MultiMap:
V remov
11 matches
Mail list logo
