[dcl.type.decltype] "operand" for specifiers

Open Beginner friendly
#9,342 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
tex
Domain
documentation

Research direction

Start with the [dcl.type.decltype]/1 and /2 and [dcl.type.auto.deduct]/4 clauses cited in the issue. Review the surrounding terminology, then replace “operand” with “expression” where proposed; done means all three passages consistently use the requested wording and the draft remains correctly rendered.

Written by the indexing model from the issue text.

Description

[dcl.type.decltype]/1 says

... The operand of the decltype specifier is an unevaluated operand.

However decltype is not an operator (even though it looks like one).

Perhaps it's better to say

... The operand expression of the decltype specifier is an unevaluated operand.

Similarly [dcl.type.decltype]/2

If the operand expression of a decltype-specifier is a prvalue and is not a (possibly parenthesized) immediate invocation ([expr.const.imm]), ...

[dcl.type.auto.deduct]/4

... The type deduced for T is determined as described in [dcl.type.decltype], as though E had been the operand expression of the decltype.

Dominant language
TeX
Stars
221
Forks
813
Avg merge
17h 45m
Merged PRs (30d)
34

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cplusplus/draft

All issues in cplusplus/draft

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.