W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2015

[Bug 28632] map:merge and timezones

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 May 2015 16:53:57 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28632-523-MCqk3XrMH5@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28632

Josh Spiegel <josh.spiegel@oracle.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #4 from Josh Spiegel <josh.spiegel@oracle.com> ---
I agree with the WG decision in comment 3.  

I would also like the definition of map:merge to clarify which key is kept when
multiple input entries have the *same key*.  

For example:

   let $m := map:merge((
       map { xs:double("1") : () },
       map { xs:integer("1"): () }
     ))
   return
     map:keys($m) instance of xs:integer

Does this evaluate to:

  (1) true
  (2) false
  (3) either (implementation-dependent)

Here is another example:

  let $m := map { 
       xs:decimal("1.00000000000000000000000000000000001") : (),
       xs:decimal("1.00000000000000000000000000000000002") : ()
    }
  return
    map:merge(($m, map:entry(xs:double("1"), "x")))

$m has two distinct entries and the incoming double key compares equal to both.
 What is the result of this query?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 19 May 2015 16:53:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 19 May 2015 16:53:59 UTC