-
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: Defining each kind of built-in exotic in one place #3211
Comments
Sounds good to the editors. I would replace 10.4 with a section which lists and links to all of the places where exotics are defined in the spec, and mention in that section that the list is not exhaustive because hosts can add other kinds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most kinds of built-in exotic object are defined in two places:
Is this separation useful? Maybe it would be better if, for each kind of built-in exotic, the two sections were brought together. (They'd still be separate, but they'd be adjacent under a single heading.)
Specifically, we could move:
10.4.2 Array Exotic Objects into 23.1 Array Objects
10.4.3 String Exotic Objects into 22.1 String Objects
10.4.5 Integer-Indexed Exotic Objects into 23.2 TypedArray Objects
10.4.6 Module Namespace Exotic Objects into 28.3 Module Namespace Objects
10.5 Proxy Object Internal Methods and Internal Slots into 28.2 Proxy Objects
and possibly:
10.4.1 Bound Function Exotic Objects into 20.2.3.2 Function.prototype.bind
10.4.4 Arguments Exotic Objects into 10.2.11 FunctionDeclarationInstantiation
10.4.7 Immutable Prototype Exotic Objects into 20.1.3 Properties of the Object Prototype Object
The text was updated successfully, but these errors were encountered: