Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

%ForInIteratorPrototype% "is never directly accessible to ECMAScript code" #14

Closed
senocular opened this issue Oct 26, 2022 · 1 comment · Fixed by #15
Closed

%ForInIteratorPrototype% "is never directly accessible to ECMAScript code" #14

senocular opened this issue Oct 26, 2022 · 1 comment · Fixed by #15

Comments

@senocular
Copy link

Will the "is never directly accessible to ECMAScript code" language in the spec need to change for intrinsics like this or should they be omitted from the values accessible through getIntrinsic()?

The %ForInIteratorPrototype% object:
...

  • is never directly accessible to ECMAScript code.

https://tc39.es/ecma262/#sec-%foriniteratorprototype%-object

@ljharb
Copy link
Member

ljharb commented Oct 26, 2022

Anything otherwise inaccessible would need to remain so, so thus one would need to be explicitly excluded. Thanks for the callout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants