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. Other resource exhaustion conditions cause the same problems.
See <https://code.google.com/p/google-caja/issues/detail?id=460>
On Mon, Jun 30, 2014 at 1:59 PM, Anne van Kesteren <annevk@annevk.nl> wrote:
> On Mon, Jun 30, 2014 at 6:01 PM, Boris Zbarsky <bzbarsky@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. :(
>
> Paging Allen. If defining this needs to start anywhere, it would
> probably be ECMAScript.
>
>
> --
> http://annevankesteren.nl/
> _______________________________________________
> es-discuss mailing list
> es-discuss@mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
--
Cheers,
--MarkM
Received on Tuesday, 1 July 2014 00:27:49 UTC