Boris Zbarsky wrote:
On 11/12/13 11:07 PM, David Bruant wrote:
I understand the need to know when a promise has an unhandled error at
development time, I'm less clear on why you need to know it at runtime.
Why would you do with this information? handle the error?
The same thing that sites (e.g. Facebook) do with window.onerror:
phone home to the server about the bug so it can actually get fixed.
Yes, good point.
I want to state what should be obvious: say we do add weak refs. Then in
a post-GC (but still serialized) phase where weak reference
notifications might happen (end of current event loop turn, say), the
slow script dialog and other anti-DoS measures are still in effect. This
means not all notifications may run.
So not only is GC non-determinism an issue for anyone trying to hook
into weak ref notification, but canceled notification phase must be
allowed in browsers. Any system using weak refs must therefore cope with
a lost notification.
/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
