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

Should Record.prototype.__proto__ be null? #104

Closed
littledan opened this issue Mar 9, 2020 · 2 comments
Closed

Should Record.prototype.__proto__ be null? #104

littledan opened this issue Mar 9, 2020 · 2 comments

Comments

@littledan
Copy link
Member

@ljharb proposed this in #71 (comment) . I'm splitting it off into a separate issue so we can give this proper discussion.

My intuition would either be that all Record wrappers have a null prototype, or it goes up to Object (I'm open to either of those); I don't quite understand the motivation for this intermediate position, but I don't see any big problems with it.

@littledan
Copy link
Member Author

For the Stage 2 draft, as per #71 (comment) , the current plan is that Record.prototype will be null ("Plan A"). For Stage 3, we'll be making a final decision between that and another plan ("Plan B") where we would have a Record.prototype, and also open to discuss other ideas. If Record.prototype is not null, I'm fine with making Record.prototype.__proto__ null, for the reasons @ljharb suggested. I'm making this as "Stage 3" since it's dependent on that other decision that we're open to reconsidering until Stage 3.

@littledan littledan added this to the stage 3 milestone Jun 1, 2020
@rricard
Copy link
Member

rricard commented Jul 8, 2022

Per the decision on #71, Records have null prototypes so there cannot be a __proto__ on it.

@rricard rricard closed this as completed Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants