Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign up[[TypedArrayConstructorName]] no longer needed #271
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ljharb
Dec 21, 2015
Member
No objections or concerns from me :-) but just in case, I wanted to point to my which-typed-array module whose behavior indirectly depends on the [[TypedArrayName]] internal slot of instances, which are currently populated via the [[TypedArrayConstructorName]] mechanism (and will remain correctly populated in each AllocateTypedArray call with @allenwb's suggested changes).
|
No objections or concerns from me :-) but just in case, I wanted to point to my which-typed-array module whose behavior indirectly depends on the |
allenwb commentedDec 21, 2015
The [[TypedArrayConstructorName]] internal slot of TypedArray constructors is no longer needed now that the secondary prototype walk has been eliminated by the changes made in the 2015-12-20 draft.
[[TypedArrayConstructorName]] was formally needed because each of the individual TypedArray constructors
supercalled to %TypedArray% and that shared constructor algorithm needed a way to identify the element type of the instance being constructed.However, with the recent changes, each TypedArray constructor is a distinct function. Hence, the desired element type can be literally coded within each constructor.
Here is sketch of the changes that need to be make: