I believe that under "Errors and Optimization", NaN is a legitimate result.
Once an xs:double NaN value has been found in the input sequence, the only
possible outcomes are NaN or an error, so the processor is entitled to take an
early bath and return NaN.
You are receiving this mail because:
You are the QA Contact for the bug.