W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2014

[Bug 24726] map:new() and map:merge()

From: <bugzilla@jessica.w3.org>
Date: Thu, 20 Mar 2014 17:12:09 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24726-523-0Cbbqt9zPn@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24726

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #4 from Michael Kay <mike@saxonica.com> ---
The XSL WG telcon looked at this today briefly; we didn't feel ready to make a
decision but there was some sympathy to the idea of keeping the map:new#0
function to create an empty map, and renaming map:new#1 as map:merge#1.

Given that we can also create a new map using the XPath 3.1 syntax map{}, the
only real case for keeping map:new#0 is the transitional benefit that it
provides a way of creating a map using functions alone, without relying on new
syntax. But if the only purpose is transitional, then map:merge(()) (merging an
empty set of maps to create an empty map) might be good enough for the
requirement.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 20 March 2014 17:12:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:46 UTC