Closed legendecas closed 4 years ago
Good catch. This should be InitializeBinding(dn, privateName).
Is anyone interested in making a PR to correct the typo?
I can't find this error in any of the three spec PRs (https://github.com/tc39/ecma262/pull/1655, https://github.com/tc39/ecma262/pull/1667, https://github.com/tc39/ecma262/pull/1668); perhaps it's been fixed in those already?
I can't find this error in any of the three spec PRs (tc39/ecma262#1655, tc39/ecma262#1667, tc39/ecma262#1668); perhaps it's been fixed in those already?
IIUC this proposal has not been merged into ecma262 yet.
I can't find this error in any of the three spec PRs (tc39/ecma262#1655, tc39/ecma262#1667, tc39/ecma262#1668); perhaps it's been fixed in those already?
Step 2.12.2.8.a.ii and 2.12.2.8.a.iii are missing in https://github.com/tc39/ecma262/pull/1655 yet presented in https://tc39.es/proposal-class-fields/#runtime-semantics-class-definition-evaluation.
@legendecas they haven’t been merged, but those three open PRs represent what will be merged eventually. If there’s something missing, please comment on it with specifics :-)
https://tc39.es/proposal-class-fields/#runtime-semantics-class-definition-evaluation
Step 2.12.2.8.a.ii created a
privateName
yet is not used afterwards. It may be used at 2.12.2.8.a.iii since the step isPerform ! classPrivateEnvRec.InitializeBinding(dn, dn).
, in which InitializeBinding might accept the name and an initializer, but in the spec two identicaldn
are used.