You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
b. Let F be CreateBuiltinFunction(defaultConstructor, 0, className, « [[ConstructorKind]], [[SourceText]] », the current Realm Record, constructorParent).
This makes the subsequent assignments invalid:
Set F.[[PrivateMethods]] to instancePrivateMethods.
Set F.[[Fields]] to instanceFields.
It's probably sufficient to add these two to the additional internal slots list passed to CreateBuiltinFunction.
Additionally, InitializeInstanceElements is being invoked from within the synthesized constructor's abstract closure, passing the active function object:
vi. Perform ? InitializeInstanceElements(result, F).
The AO has its argument typed as "an ECMAScript function object" and performs the same field access, which is problematic for the same reasons.
The text was updated successfully, but these errors were encountered:
Adding the slots makes sense to me, and the AO certainly should check for the presence of the X slot before accessing it, either with an early return or with a type assertion on the parameter.
These are only present in ECMAScript Function Objects, however in the absence of a
constructor
method the function object is created as a Built-in Function Object:This makes the subsequent assignments invalid:
It's probably sufficient to add these two to the additional internal slots list passed to CreateBuiltinFunction.
Additionally, InitializeInstanceElements is being invoked from within the synthesized constructor's abstract closure, passing the active function object:
The AO has its argument typed as "an ECMAScript function object" and performs the same field access, which is problematic for the same reasons.
The text was updated successfully, but these errors were encountered: