On 2015/02/25 11:21:18, Dmitry Lomov (chromium) wrote:
1. Writing experimental prototype CLs and seeking feedback is fine and greatly
encouraged as long as those CLs are clearly marked as such.
2. I am not convinced that now is the right time to land exponentiation
operator
in V8:
    - we are in time of great churn, what with all the ES6 features and
TurboFan
trying to replace Crankshaft
    - you see for yourself that this Cl ends up being pretty invasive and a
moving part on top of a bunch of other moving parts
    - it is not that we see a high demand for exponentiation operator being
implemented in V8 at this point
- once this lands, we need to support exp operator throughout any and all changes and refactorings we need to do. To really get exp operator support on
par with other arithmetic operators we have, we would need to implement
BinaryOpIC support for it and so on and so forth - I do not think we have
bandwidth at this point to do this.

So my recommendation would be to not land this at this point of time.

I agree with what Dmitry said. A new primitive operator is a rather intrusive feature, and we have more than enough loose ends to deal with at the moment. I
prefer to focus on our current priorities (ES6, Turbofan, strong mode), and
avoid broadening the surface of the language & system further before we are
through with all that.

That said, we of course welcome experimentation. To address Michael's concerns,
it would help if the description of experimental CLs clearly stated the
intention (in particular, when there is no intent to land; an explicit heads-up reply is appreciated once such a CL is emerging from experimental to "real").

https://codereview.chromium.org/953563002/

--
--
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/d/optout.

Reply via email to