Sure, the optimization I'm suggesting isn't there yet. It's just "the right
thing to do".
Your implementation is not only pretty hacky, but also wrong. E.g., you only
deoptimize while overwriting the property through the runtime. An
assignment via
IC or Crankshaft would not trap, and would lead to wrong semantics.
We don't want to pollute all paths of the code for such a "simple
optimization"
that can be automatically covered by a wider applicable optimization.
https://codereview.chromium.org/198533007/
--
--
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.
