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: Shorten the conditions in the [[Set]] algorithm #713

Merged
merged 1 commit into from Apr 16, 2019

Conversation

Ms2ger
Copy link
Member

@Ms2ger Ms2ger commented Apr 15, 2019

An interface can only have a (named or indexed) setter if it also has the
corresponding getter, so checking for both is unnecessary.

An interface can only have a (named or indexed) setter if it also has the
corresponding getter, so checking for both is unnecessary.
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

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

I looked at this in context and the conventions in [[DefineOwnProperty]] are different. Perhaps we should aim to remove "supports" altogether as it's rather meaningless?

@Ms2ger
Copy link
Member Author

Ms2ger commented Apr 16, 2019

[[DefineOwnProperty]] is different because it has to handle the case where the interface has a getter but no setter. [[Set]] doesn't.

@Ms2ger Ms2ger merged commit 059491b into master Apr 16, 2019
@Ms2ger Ms2ger deleted the lpo-set-shorten branch April 16, 2019 14:18
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.

None yet

2 participants