Status: Accepted
Owner: [email protected]
CC: [email protected]
Labels: Type-Bug Priority-Medium
New issue 4058 by [email protected]: [strong] Figure out what to do with
lazy parsing in strong mode
https://code.google.com/p/v8/issues/detail?id=4058
... many of the strong mode checks (especially those related to checking
variable uses against declarations) don't work inside lazy functions.
There are some alternatives on what to do about it:
1) Make PreParser always track identifiers & gather variables into scopes,
and if we're in strong mode, do the scope analysis & strong mode checks.
This is a 5% code load regression. CL for tracking identifiers:
https://codereview.chromium.org/918203002/
2) Make PreParsers track identifiers only inside strong mode
This requires that the new "PreParserIdentifier" (or such) sometimes is an
AstString* and sometimes not. Not sure how this would work.
3) Other options and hacks. Never lazy parse in strong mode? Ugh. Developer
mode for strong mode? (That wouldn't enable us to skip any run-time checks
later.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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.
