I also tried digging into it, but without much success. Something must be
pointing into the wild, but I couldn't find out what.
Some cases fail with an invalid access. I'd try to breakpoint on those in
the
debugger and try to figure out what there pointing at and where it is coming
from. Maybe that gives a hint.
The next thing you could try is not invoking DeclareParameter on the rest
param
at all, and just desugar using a temporary instead. In fact, it should be
possible to make it such that all traces of a rest parameter effectively
disappear after desugaring. (The only thing you probably need to remember is
whether the parameter list was simple, for allocating the right arguments
object
later.)
You could also try to temporarily replace the desugaring with a nop. If that
doesn't make the problem go away then maybe something is f-ed up with
variable/temporary allocation?
Maybe there also is some weird problem with doing the desugaring after
processing the body. Could be worth a shot trying to undo that (with the
TC39
resolution it doesn't seem necessary anymore anyway).
https://codereview.chromium.org/1272673003/
--
--
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.
