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

[Bug 29586] [XQ31] The judgement subtype-itemtype(Ai, Bi)

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 May 2016 09:54:40 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29586-523-vKaOo6al5z@http.www.w3.org/Bugs/Public/>

--- Comment #6 from John Snelson <john.snelson@marklogic.com> ---
(In reply to Tim Mills from comment #3)
> This appears to prevent a processor from using static type analysis to avoid
> unnecessary function coercion.  For example, I think this requires that
> function() { 1 } instance of function() as xs:integer
> returns false.

I agree that your expression above should return false. I think it would be
reasonable to allow an implementation to determine a stricter return type for
the inline function using static typing if it can.

Of course, your own static typing implementation could easily carry two types
for the inline function expression - the "official" static type, and a static
type for the way it behaves in practice. That would allow you to avoid the
function coercion you were worried about.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 May 2016 09:54:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 3 May 2016 09:54:44 UTC