Don't treat catch scopes as possibly-shadowing for sloppy eval

src/ast/scopes.cc

Index: src/ast/scopes.cc
diff --git a/src/ast/scopes.cc b/src/ast/scopes.cc
index 2372e1bb1d4b944a4acb668d1ff325c9199d0fd3..2f99a29d5919b51d7a8a6ccd675b03b23eb9faec 100644
--- a/src/ast/scopes.cc
+++ b/src/ast/scopes.cc
@@ -1098,7 +1098,7 @@ Variable* Scope::LookupRecursive(VariableProxy* proxy,
     if (var != NULL && proxy->is_assigned()) var->set_maybe_assigned();
     *binding_kind = DYNAMIC_LOOKUP;
     return NULL;
-  } else if (calls_sloppy_eval() && !is_script_scope() &&
+  } else if (calls_sloppy_eval() && !is_script_scope() && !is_catch_scope() &&

[Dan Ehrenberg, 2016/05/04 20:54:08]

Can anything besides a function_scope have variable bindings be shadowed by a
sloppy eval call?

[adamk, 2016/05/04 21:06:18]

We also must consider block scopes which are marked as "declaration scopes"
(called "varblock" elsewhere), as well as eval scopes.

              name_can_be_shadowed) {
     // A variable binding may have been found in an outer scope, but the current
     // scope makes a sloppy 'eval' call, so the found variable may not be