29260 2015-11-03 19:41:37 +0000 Array Tests: function tests 2015-11-10 17:21:59 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3.1 Candidate Recommendation PC Windows NT RESOLVED FIXED P2 normal --- 1 christian.gruen jonathan.robie public-qt-comments oldest_to_newest 124069 0 christian.gruen 2015-11-03 19:41:37 +0000 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." 124157 1 jonathan.robie 2015-11-10 17:21:59 +0000 I'll do this.