Comment #2 on issue 4182 by [email protected]: Construct TypedArrays
with AllocateTypedArray
https://code.google.com/p/v8/issues/detail?id=4182
The TypedArrays spec is very interesting. For this performance-motivated
feature, most code is in the polymorphic location of %TypedArray%
and %TypedArray%.prototype . Performance aside (I think we'll have to clone
whole method bodies to get good performance on workloads which use multiple
TypedArray types), this poses a challenge for the way constructors work.
The spec basically requires that each TypedArray constructor gets its
constructor behavior by calling super(). The super constructor is only
usable in a class literal, and I can't use that for TypeArrays since the
TypedArray constructors already exist as intrinsics. The other way to do
this is Reflect.construct.
Currently, however, ES6 reflection features are incomplete and held behind
a flag (even if Reflect.construct seems to work). Shutting off the flag
stops $reflectConstruct from being exposed to Javascript (not just
preventing src/harmony-reflect from being loaded).
Should this bug wait until reflection is done? How ready is
Reflect.construct now; would it make sense to just expose it to internal
Javascript early for use cases like this?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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.
