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: tweak PropertyDefinitionEvaluation and ClassElementEvaluation #2470

Merged
merged 2 commits into from
Jul 28, 2021

Conversation

bakkot
Copy link
Contributor

@bakkot bakkot commented Jul 22, 2021

For the first commit: The _enumerable_ parameter for PropertyDefinitionEvaluation was always true; the parameter of the same name for ClassElementEvaluation was always false. Prior to #1668 PropertyDefinitionEvaluation was used for both object literals and classes. When it was split, the parameter became redundant.

The second commit just fixes an oversight of mine from fe6b5ef (part of #2271).

@michaelficarra michaelficarra added the ready to merge Editors believe this PR needs no further reviews, and is ready to land. label Jul 28, 2021
@ljharb ljharb force-pushed the propertydefinitionevaluation branch from b0fb7bc to 99b36f0 Compare July 28, 2021 22:23
@ljharb ljharb merged commit 99b36f0 into master Jul 28, 2021
@ljharb ljharb deleted the propertydefinitionevaluation branch July 28, 2021 22:26
mathiasbynens pushed a commit to mathiasbynens/ecma262 that referenced this pull request Oct 18, 2021
mathiasbynens pushed a commit to mathiasbynens/ecma262 that referenced this pull request Oct 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial change ready to merge Editors believe this PR needs no further reviews, and is ready to land.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants