Okay, I've convinced myself that fixing the debugger here is going to be
tricky,
and that there's something _almost_ semantically correct about showing this
extra block scope in the debugger (it represents the state of the
loop-declared
variables just outside the loop).
I'll still aim to fix the debugger asap, but I agree that correctness here
is
the most important thing (especially because Edge gets this right, and I've
found almost-real code in our unittests which ran afoul of this tdz).
https://codereview.chromium.org/1218543003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
