Private fields

src/flag-definitions.h

Index: src/flag-definitions.h
diff --git a/src/flag-definitions.h b/src/flag-definitions.h
index 653732b05db325841ab0fba598f233f656068a45..78e6771f27c718fe83c2a1bfd341edd408b5b8d8 100644
--- a/src/flag-definitions.h
+++ b/src/flag-definitions.h
@@ -203,7 +203,8 @@ DEFINE_IMPLICATION(es_staging, move_object_start)
   V(harmony_for_in, "harmony for-in syntax")                            \
   V(harmony_trailing_commas,                                            \
     "harmony trailing commas in function parameter lists")              \
-  V(harmony_class_fields, "harmony public fields in class literals")
+  V(harmony_class_fields, "harmony public fields in class literals")    \
+  V(harmony_private_class_fields, "harmony private fields in class literals")

[Dan Ehrenberg, 2016/09/10 04:30:28]

Looks like this patch assumes that, if --harmony-private-class-fields is on,
then --harmony-class-fields is on. To make ClusterFuzz happy, we should set this
up as an explicit dependency, otherwise it'll test one without the other. You
can do this with DEFINE_IMPLICATION.

[bakkot, 2016/09/13 01:05:38]

It doesn't; they can be used independently. All of the places where both patches
need it check whether either is on. Most of the tests only have
--harmony-private-class-fields, though some have both.

 
 // Features that are complete (but still behind --harmony/es-staging flag).
 #define HARMONY_STAGED_BASE(V)                                               \