Thank you very much for the information.
On Tue, Jul 1, 2014 at 9:27 AM, Mark S. Miller erig...@google.com wrote:
I would like to see us take a principled stance on resource exhaustion
errors in ES7. This includes both stack and heap, and both space and time.
For example, the browser
On Mon, Jun 30, 2014 at 10:27 AM, Yutaka Hirano yhir...@google.com wrote:
But it is unclear to me whether a stack overflow exception is counted
as an exception thrown inside an event listener.
Are stack overflow exceptions even a thing per standards?
On 6/30/14, 4:40 AM, Anne van Kesteren wrote:
Are stack overflow exceptions even a thing per standards?
No.
However, they come up pretty regularly in practice. In fact, some sites
depend on them for proper functioning. :(
-Boris
On Mon, Jun 30, 2014 at 6:01 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/30/14, 4:40 AM, Anne van Kesteren wrote:
Are stack overflow exceptions even a thing per standards?
No.
However, they come up pretty regularly in practice. In fact, some sites
depend on them for proper functioning.
I would like to see us take a principled stance on resource exhaustion
errors in ES7. This includes both stack and heap, and both space and time.
For example, the browser behavior on terminating a turn that takes too long
and proceeding silently to the next turn leaves arbitrary invariants
broken.
