- From: <bugzilla@jessica.w3.org>
- Date: Sun, 10 Jul 2016 09:33:06 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29722 --- Comment #2 from Michael Kay <mike@saxonica.com> --- I agree that the handling of collations in these functions isn't very satisfactory. As currently specified, because they invoke deep-equal#2, the default collation kicks in automatically for string-valued keys; including the case where the key is actually the output of a call to collation-key(), which isn't very satisfactory. Two possible ways we could go: (a) add a collation argument to the functions, and specify the result in terms of a call to deep-equal() supplying that collation. (b) define the call on deep-equal to use codepoint collation, and rely on use of collation-key() if the user wants to do collation-based sorting. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 10 July 2016 09:33:13 UTC