[es6] fix nested object literals with computed property names

src/ast.cc

Index: src/ast.cc
diff --git a/src/ast.cc b/src/ast.cc
index 624d462323a9574c278af3e01a240976509239ac..eea011034cfcb7761f5a5a3506cf05afcc547315 100644
--- a/src/ast.cc
+++ b/src/ast.cc
@@ -433,7 +433,8 @@ void ObjectLiteral::BuildConstantProperties(Isolate* isolate) {
 
   int position = 0;
   // Accumulate the value in local variables and store it at the end.
-  bool is_simple = true;
+  // If computed properties are used, the literal is never simple.
+  bool is_simple = boilerplate_properties_ != 0 || properties()->length() == 0;

[wingo, 2015/08/24 16:04:40]

I am missing a bit of context.  Is boilerplate_properties always zero if there
are computed properties?  As an ignorant reader I would appreciate a
has_computed_properties() predicate :)

[caitp (gmail), 2015/08/24 16:08:27]

yeah, it can be organized that way for sure. I'm not totally sure why we don't
save the `has_computed_properties` flag in the literal, which is computed by the
parser already

   int depth_acc = 1;
   uint32_t max_element_index = 0;
   uint32_t elements = 0;