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: remove some unnecessary "the result of" phrasing #3346

Merged
merged 1 commit into from
Jul 9, 2024

Conversation

michaelficarra
Copy link
Member

This aligns well with our editorial convention of avoiding "the value of".

spec.html Outdated
@@ -9260,7 +9260,7 @@ <h1>
1. If |ClassHeritage| is present, return *true*; otherwise return *false*.
1. If |ClassHeritage| is present, then
1. If |ClassHeritage| Contains _symbol_ is *true*, return *true*.
1. Return the result of ComputedPropertyContains of |ClassBody| with argument _symbol_.
1. Return ComputedPropertyContains of |ClassBody| with argument _symbol_.
Copy link
Contributor

@bakkot bakkot Jun 6, 2024

Choose a reason for hiding this comment

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

This reads weirdly to me; I would much prefer to keep the previous form, here and in most of the cases involving an AO or SDO invocation below.

Copy link
Member Author

Choose a reason for hiding this comment

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

Can you be more specific about which cases, or try to define a general rule?

@michaelficarra michaelficarra added the editor call to be discussed in the next editor call label Jun 13, 2024
spec.html Outdated
@@ -9214,7 +9214,7 @@ <h1>
1. For each child node _child_ of this Parse Node, do
1. If _child_ is an instance of _symbol_, return *true*.
1. If _child_ is an instance of a nonterminal, then
1. Let _contained_ be the result of _child_ Contains _symbol_.
1. Let _contained_ be _child_ Contains _symbol_.
Copy link
Contributor

Choose a reason for hiding this comment

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

I like the old form better for Contains.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agreed, though I'm not a huge fan of using infix notation for Contains in the first place.

spec.html Outdated Show resolved Hide resolved
@michaelficarra michaelficarra removed the editor call to be discussed in the next editor call label Jul 3, 2024
@michaelficarra michaelficarra added the ready to merge Editors believe this PR needs no further reviews, and is ready to land. label Jul 9, 2024
@ljharb ljharb merged commit 7d0b199 into main Jul 9, 2024
8 checks passed
@ljharb ljharb deleted the the-result-of branch July 9, 2024 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial change establishes editorial conventions 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.

4 participants