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

Editorial: Defining each kind of built-in exotic in one place #3211

Open
jmdyck opened this issue Oct 29, 2023 · 1 comment
Open

Editorial: Defining each kind of built-in exotic in one place #3211

jmdyck opened this issue Oct 29, 2023 · 1 comment

Comments

@jmdyck
Copy link
Collaborator

jmdyck commented Oct 29, 2023

Most kinds of built-in exotic object are defined in two places:

  • a section within 10.4 that gives the internal methods/slots, and
  • a section within 20-28 that defines intrinsics (constructor, prototype, methods, properties).

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:

and possibly:

@michaelficarra michaelficarra added the editor call to be discussed in the next editor call label Jan 3, 2024
@bakkot
Copy link
Contributor

bakkot commented Jan 10, 2024

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.

@bakkot bakkot removed the editor call to be discussed in the next editor call label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants