W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2016

[Bug 29449] [xslt 3.0] Streamability of $map($key) and $array($index)

From: <bugzilla@jessica.w3.org>
Date: Mon, 15 Feb 2016 16:27:17 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29449-523-Tniv4DM00q@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29449

Michael Kay <mike@saxonica.com> changed:

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

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
Resolution: add a note to the spec along the following lines:

Note that in a dynamic function call $F($A), the operand usage of $F is
inspection, so what is passed to $F has no direct bearing. As for $A, if we
know that $F is a map or array, then we know that $A has usage absorption
(because the inferred type is xs:anyAtomicType), and therefore passing a
streamed node is OK (the result will be consuming), but if we don't know that
$F is a map or array, then passing a streamed node will be
roaming/free-ranging.

So advice is users is: if you want it to be streamable, make sure $F is
declared to be a map or array, or use an alternative construct such as $F?($A)
(3.1) or map:get($F, $A).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 15 February 2016 16:27:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 15 February 2016 16:27:20 UTC