- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 Oct 2015 19:33:11 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=4378 --- Comment #12 from Josh Spiegel <josh.spiegel@oracle.com> --- Thanks for the clarification Tim. I agree that none isn't ideal because it leaves the possibility that static analysis and optimizations hide the error condition. Since it never makes sense to use the context item of the function body, why not raise a static error when an expression depends on it? While playing around with this idea, I noticed tests try-016 and try-017: https://github.com/LeoWoerteler/QT3TS/blob/a2a6b9dc40fbcd5db7a41f927c038b1b1880c489/prod/TryCatchExpr.xml#L215 Wouldn't a static error be more helpful to the user in both these cases? It would be a backwards compatibility issue to force it at this point, but allowing it might be nice... -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 1 October 2015 19:33:14 UTC