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

[Bug 24510] Absence of bind-group and bind-grouping-key need not be free-ranging

From: <bugzilla@jessica.w3.org>
Date: Fri, 14 Mar 2014 10:20:21 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24510-523-Z7TMAMKrvC@http.www.w3.org/Bugs/Public/>

--- Comment #8 from Michael Kay <mike@saxonica.com> ---
We looked at the proposal on 2014-03-13 and found some inconsistencies in the
handling of current merge group.

I've taken the opportunity to look again at this area and the revised proposal
does some refactoring of the way that current-merge-group() works. Although the
current merge group is still defined as a map, the function no longer returns
this map directly, but instead has two forms:

- the arity-1 function returns a selected entry from the map, that is, all the
merge inputs from one named merge source

- the arity-0 function returns the inputs from all merge sources, that is all
the values in the map regardless of their key.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 14 March 2014 10:20:22 UTC

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