Overall a right direction, but let's try to position default constructors
in the
source - then many changes are not needed
https://codereview.chromium.org/700523003/diff/1/src/parser.cc
File src/parser.cc (right):
https://codereview.chromium.org/700523003/diff/1/src/parser.cc#newcode1016
src/parser.cc:1016: shared_info->is_default_constructor_call_super(),
scope);
I believe if you set positions correctly all this can be handled
downstream in ParseLazy(&stream) so that you do not need to duplicate
all this set-up.
https://codereview.chromium.org/700523003/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
