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

[Bug 29470] [xslt30] Polyfills

From: <bugzilla@jessica.w3.org>
Date: Tue, 16 Feb 2016 13:47:32 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29470-523-FsXKCC7oOb@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29470

Michael Kay <mike@saxonica.com> changed:

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

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
While recognizing the benefits, we also found some complications:

(a) It's not clear what the effect on static expressions would be

(b) It could be disruptive for some implementations that make built-in
assumptions about the behaviour of built-in functions

(c) We might need rules about compatibility of signatures between a polyfill
function and the built-in version.

So we're abandoning the proposal for now.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 16 February 2016 13:47:43 UTC

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