Yep, as suspected, we need to put this new functionality behind the
--harmony
flag. The easiest way to do this that I can think of is to move the methods
into
a separate JS file (e.g. harmony.js) that is evaluated after context
deserialization. If you take a look at
Genesis::InstallExperimentalNatives(),
you'll see how that's done for the other features. Inside the harmony.js
file
there should then be some SetUpHarmonyString() method that extends the
existing
string prototype with the new ES6 functions. AFAICT the InstallFunctions()
helper should be flexible enough to be called twice on the same object. This
applies to all three of your CLs.
https://codereview.chromium.org/20928002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
