Re: Discussion of op:same-key

On 02/06/2016 13:35, Abel Braaksma wrote:
> I am surprised about example below, surely because "xs:float(33554433) eq 33554433 = true()", one would expect "no surprise" to be returned?
This is the main argument for reviewing op:same-key.  The behaviour 
above is surprising but not implementation-dependent.  Other behaviours 
are surprising and vary by implementation.  The pain of implementation 
comes in third, behind the high cost of computing the keys for the map.

The above is surprising unless one is familiar with the range of integer 
values which can be exactly represented by a floating point value.

Cheers,
     Tim

Received on Thursday, 2 June 2016 13:13:06 UTC