Hey Jaro,
This code is awkward and inherently native context dependent, plus we don't
need
it (at least for now). I confirmed that we never hit this by adding
CHECK(false)
to the branch and running test suites and benchmarks. I think the correct
way to
deal with constructors on the global object is to either have them
recognized
with builtin function id or via special global load support (which I'm
working
on now), or both.
Please take a look.
Thanks,
Benedikt
Andreas: FYI
https://codereview.chromium.org/1221683006/
--
--
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.
