Another high-level comment below. Performance aside, we should try to get
the
behavior correct.
https://codereview.chromium.org/1308123007/diff/1/test/mjsunit/harmony/destructuring.js
File test/mjsunit/harmony/destructuring.js (right):
https://codereview.chromium.org/1308123007/diff/1/test/mjsunit/harmony/destructuring.js#newcode959
test/mjsunit/harmony/destructuring.js:959: assertDoesNotThrow("function
f({x}) { var x; }; f({});");
So this is no longer an error, but yet
function f({x = undefined}) { var x; }
is an error.
Seems like there's a deeper problem here. I need to tech up my
spec-reading to fully grok IteratorBindingInitialization, but it seems
like the let-binding-ness shouldn't have anything to do with the
ContainsExpression bit.
https://codereview.chromium.org/1308123007/
--
--
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.
