Allow lazy parsing of functions nested in eager compiled functions

src/parsing/parse-info.cc

Index: src/parsing/parse-info.cc
diff --git a/src/parsing/parse-info.cc b/src/parsing/parse-info.cc
index 927dea86165ab96e2710aadb7a194bed3b7bd458..1d3700c135258b3c9200495e378759c3166c91fd 100644
--- a/src/parsing/parse-info.cc
+++ b/src/parsing/parse-info.cc
@@ -39,6 +39,7 @@ ParseInfo::ParseInfo(Zone* zone, Handle<SharedFunctionInfo> shared)
   isolate_ = shared->GetIsolate();
 
   set_lazy();
+  set_allow_lazy_parsing(true);

[jochen (gone - plz use gerrit), 2016/10/10 12:33:25]

what's the difference between set_lazy and set_allow_lazy_parsing given that the
struct is called ParseInfo?

[Toon Verwaest, 2016/10/10 14:18:52]

is_lazy is a misnomer. It should be called "eager_parse_function". It's when you
have a Handle<JSFunction> and you want to parse/compile it; as opposed to a
script.

   set_hash_seed(isolate_->heap()->HashSeed());
   set_is_named_expression(shared->is_named_expression());
   set_calls_eval(shared->scope_info()->CallsEval());