Skip to content

Add an algorithm to create a platform object. #635

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

Merged
merged 1 commit into from
Feb 22, 2019
Merged

Conversation

Ms2ger
Copy link
Member

@Ms2ger Ms2ger commented Jan 31, 2019

@Ms2ger
Copy link
Member Author

Ms2ger commented Jan 31, 2019

This is partially based on the algorithm in #595, and there's still a bunch of declarative requirements that could move into this, but I wanted to take small steps.

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost there, woohoo.

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going to say LGTM, although indeed "this" instead of "this value" would probably be good. We can fix that up as part of the follow-up mentioned, though.

@bzbarsky
Copy link
Collaborator

Note that this doesn't match Gecko if NewTarget has a prototype property that isn't an object.

Yep, Gecko doesn't have access to a thing that implements the per-spec behavior of GetFunctionRealm, for example. See https://bugzilla.mozilla.org/show_bug.cgi?id=1529757 and https://bugzilla.mozilla.org/show_bug.cgi?id=1317658

Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, please land!

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

Successfully merging this pull request may close these issues.

7 participants