Thanks for posting this! It brings up a case I hadn't yet thought of, that
of a destructuring assignment _inside_ a destructuring bind:
((x, {y = ({z} = x)}) => y)({z: 1}, {})
should return 1
I don't _think_ this is any more problematic (once parsed), but it's
definitely....tricky.
On Thu, Oct 15, 2015 at 8:50 PM, Caitlin Potter <[email protected]>
wrote:
> I've tried to assemble the various informal design decisions around
> implementing Destructuring Assignment into a single place
>
> Here: https://etherpad.igalia.com/1869 --- To summarize, in my head, it
> looks like most of this should be
> doable with fairly simple refactoring to the pattern-rewriter, and the
> mechanism for rewriting destructuring assignment that exists in my
> destructuring assignment parsing CL (https://crrev.com/1309813007/).
>
> Comments and edits are appreciated
>
> --
> --
> 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.
>
--
--
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.
