- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 24 Jan 2008 03:37:27 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5288 ------- Comment #5 from mrys@microsoft.com 2008-01-24 03:37 ------- Actually, the problem I see Tim report is that none is inferred for error() instead of an error type that could be preserved. Note that in almost all cases, non-error() containing expressions that statically yield empty-sequence() are because of a programmer's mistake and this raising the error is good in all of these cases. While the biggest use-case is path expressions, there are many other places as Mike notes. Also note that changing this rule as an errata is not acceptable, since it impacts existing implementations.
Received on Thursday, 24 January 2008 03:37:37 UTC