Chromium Code Reviews| Index: src/bootstrapper.cc |
| diff --git a/src/bootstrapper.cc b/src/bootstrapper.cc |
| index 31d6e3e00c2cc355bc8b2caaface11a6989d55bd..67a7c299d8259b5015b0313e359aaa23a91e038d 100644 |
| --- a/src/bootstrapper.cc |
| +++ b/src/bootstrapper.cc |
| @@ -1615,6 +1615,8 @@ EMPTY_NATIVE_FUNCTIONS_FOR_FEATURE(harmony_unicode) |
| EMPTY_NATIVE_FUNCTIONS_FOR_FEATURE(harmony_unicode_regexps) |
| EMPTY_NATIVE_FUNCTIONS_FOR_FEATURE(harmony_computed_property_names) |
| EMPTY_NATIVE_FUNCTIONS_FOR_FEATURE(harmony_rest_parameters) |
| +EMPTY_NATIVE_FUNCTIONS_FOR_FEATURE(harmony_spread) |
| +EMPTY_NATIVE_FUNCTIONS_FOR_FEATURE(harmony_spreadcalls) |
|
rossberg
2015/02/24 16:22:46
Why do we need a separate flag?
caitp (gmail)
2015/02/25 00:00:24
See the answer I gave to Erik --- If spread-calls
rossberg
2015/02/25 14:28:18
Well, since they currently imply each other, the s
|
| void Genesis::InstallNativeFunctions_harmony_proxies() { |
| @@ -1647,6 +1649,8 @@ EMPTY_INITIALIZE_GLOBAL_FOR_FEATURE(harmony_sloppy) |
| EMPTY_INITIALIZE_GLOBAL_FOR_FEATURE(harmony_unicode) |
| EMPTY_INITIALIZE_GLOBAL_FOR_FEATURE(harmony_computed_property_names) |
| EMPTY_INITIALIZE_GLOBAL_FOR_FEATURE(harmony_rest_parameters) |
| +EMPTY_INITIALIZE_GLOBAL_FOR_FEATURE(harmony_spread) |
| +EMPTY_INITIALIZE_GLOBAL_FOR_FEATURE(harmony_spreadcalls) |
| void Genesis::InitializeGlobal_harmony_regexps() { |
| Handle<JSObject> builtins(native_context()->builtins()); |
| @@ -2230,6 +2234,9 @@ bool Genesis::InstallExperimentalNatives() { |
| static const char* harmony_unicode_regexps_natives[] = {NULL}; |
| static const char* harmony_computed_property_names_natives[] = {NULL}; |
| static const char* harmony_rest_parameters_natives[] = {NULL}; |
| + static const char* harmony_spread_natives[] = {"native harmony-spread.js", |
| + NULL}; |
| + static const char* harmony_spreadcalls_natives[] = {NULL}; |
| for (int i = ExperimentalNatives::GetDebuggerCount(); |
| i < ExperimentalNatives::GetBuiltinsCount(); i++) { |