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

[Bug 29220] map-merge-003-hof, map-entry-001-hof, map-put-003-hof

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

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
XPath 2.5.5.8 says:

The function signature of the map, treated as a function, is always
function(xs:anyAtomicType) as item()*, regardless of the actual types of the
keys and values in the map. §§This means that a function item type with a more
specific return type, such as function(xs:anyAtomicType) as xs:integer, does
not match a map in the sense required to satisfy the instance of operator.§§
However, the rules for function coercion mean that any map 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 map (treated as a function) returns a
value that is not an instance of the required return type.

I think that if you are challenging this test case then you are challenging
this statement in the spec, especially the sentence I have marked with §§..§§.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 November 2015 15:43:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 November 2015 15:43:36 UTC