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

[Bug 29260] New: Array Tests: function tests

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Nov 2015 19:41:37 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29260-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29260

            Bug ID: 29260
           Summary: Array Tests: function tests
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 3.1
          Assignee: jonathan.robie@gmail.com
          Reporter: christian.gruen@gmail.com
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

This is inspired by the (closed) Bug 29220: In analogy with the map type rules,
it could make sense to explain typing of arrays in more detail. The following
paragraph or a similar one could be added to 2.5.5.9 of the XPath and XQuery
3.1 specs (...provided that it's correct):

"The function signature of the array, treated as a function, is always
function(xs:integer) as item()*, regardless of the actual member types in the
array. This means that a function item type with a more specific return type,
such as function(xs:integer) as xs:integer, does not match an array in the
sense required to satisfy the instance of operator. However, the rules for
function coercion mean that any array can be supplied as a value in a context
where such a type is the required type, and a type error will only occur if an
actual call on the array (treated as a function) returns a value that is not an
instance of the required return type."

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 November 2015 19:41:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 November 2015 19:41:41 UTC