W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2014

[Bug 26517] Methods that return promises are unable to throw exceptions

From: <bugzilla@jessica.w3.org>
Date: Tue, 07 Oct 2014 17:50:06 +0000
To: public-script-coord@w3.org
Message-ID: <bug-26517-3890-W5hDOdr94U@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26517

--- Comment #24 from Mark S. Miller <erights@gmail.com> ---
(In reply to Jonas Sicking from comment #22)
> I don't know of any APIs which have synchronous side-effects and which also
> return a promise. So you can't rely on anything having successfully happened
> on the line after the .foo() call anyway.

Just to clarify, I think that should be rephrased as "observably synchronous
side effects". For example, the enqueue and dequeue methods of
http://wiki.ecmascript.org/doku.php?id=strawman:concurrency#infinite_queue have
sync side effects, but not observably so.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 7 October 2014 17:50:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC