-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Editorial convention for referring to intrinsics #2023
Comments
The decision has already been that the dotted form should always be used, except in the Well-Known Intrinsics table, and also in the places where the non-dotted intrinsics are defined. If there are any cases that deviate from this, let's please fix them. Additionally, as soon as we can verify that HTML is no longer using an undotted form, it can and should be removed entirely from 262. |
There's a number of uses of
I think it would be worth preserving these at least in a NOTE, for documentation purposes. |
Totally fair; I'd expect that to be an entry in Annex E. |
Not sure what you mean by top-level types. Neither is directly referenceable from the global object. The way you get at |
Sure - but if they were exposed, that's what would be. Happy to chat on the call tho about preferring one over the other. Is there any contention about any of the globally-exposed intrinsics, and the intrinsics that are otherwise reachable dotting off of them? |
Well, no, it would be the object currently called
I don't really have strong opinions, I just want it to be settled and written down somewhere. |
can we rename them to |
@devsnek i'm down with that if you do the prior research and ensure HTML and 402 (and other layered specs, if any) aren't using any "old" names. |
@ljharb we would still leave the original names in the table |
The ultimate goal is to delete the old names entirely imo. |
…tted forms Fixes tc39#2023.
…tted forms Fixes tc39#2023.
…tted forms Fixes tc39#2023.
…tted forms Fixes tc39#2023.
Some intrinsics have multiple names: for example,
%AsyncGenerator%
and%AsyncGeneratorFunction.prototype%
name the same object. We should decide which we prefer, document that, and be consistent about which we use.(This came up in #1781, e.g. 51072eb.)
The text was updated successfully, but these errors were encountered: