Skip to content

Add explanation of "in", "of", "names", "denotes", and "designates"#950

Open
eisenwave wants to merge 2 commits into
mainfrom
more-wording-idioms
Open

Add explanation of "in", "of", "names", "denotes", and "designates"#950
eisenwave wants to merge 2 commits into
mainfrom
more-wording-idioms

Conversation

@eisenwave

Copy link
Copy Markdown
Member

I've had a chat in the CWG Mattermost channel, and there looks to be some appetite for explaining more CWG wording idioms.

We can start with "in" vs. "of", as well as "names"/"denotes"/"designates'. These idioms are used all the time, and it would be nice to have something to point authors at.

Comment thread wording-guidelines.md Outdated
Comment thread wording-guidelines.md Outdated
Comment thread wording-guidelines.md Outdated
appears directly in the definition of *template-parameter*,
and *type-specifier* is nested several levels deep into *parameter-declaration*
(*type-specifier* → *defining-type-specifier* → *decl-specifier* → *decl-specifier-seq*
→ *parameter-declaration*).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

... and that example shows why "in" is generally bad: The parameter-declaration can have a type-specifier in different places: as a top-level decl-specifier or as a type-specifier in a parameter-declaration of a function type that appears in the outer parameter-declaration. Maybe add a sentence explaining that?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

It turns out we already had a short description of "in" vs. "of" in the guidelines that even came with a negative example.

I've absorbed that into the new section that goes a bit more into detail now.

image

I think it's still worth the upgrade and having a dedicated section on it, just because of how common these terms are, and I'd like to keep the <dl> list element style going throughout the guidelines. It's also easier to link by #anchor if you have a dedicated subsection.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

The Tip portion also adds value because paper authors might feel forced into using "in" if there isn't a single-level, direct relationship between two things, and we wouldn't want them to get that impression. Using chains of of is also possible.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants