[expr.type] p1 should possibly be a note
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
If an expression initially has the type “reference to T” ([dcl.ref], [dcl.init.ref]), the type is adjusted to T prior to any further analysis.
The expression designates the object or function denoted by the reference, and the expression is an lvalue or an xvalue, depending on the expression.
To me it seems like this paragraph could be a note, because it doesn't provide any normative information. This paragraph does not state what kind of references are turned into lvlaues or xvalues respectively, it merely hints to the reader that such a conversion mechanism exists.
All the specifics can be found in other paragraphs, such as:
- [expr.call] p13 for function calls
- [expr.static.cast] p1 for
static_cast - ...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with [expr.type] paragraph 1 and compare its wording with the cited [expr.call] paragraph 13 and [expr.static.cast] paragraph 1. Determine whether the paragraph supplies normative information or should be presented as a note; done means the issue has a justified standards-editorial resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100