[intro.object] Does the attributive clause intend to be a constraint or to convey a result?
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
These operations select one of the implicitly-created objects whose address is the address of the start of the region of storage, and produce a pointer value that points to that object, if that value would result in the program having defined behavior.
The attributive clause in this sentence makes the rule read like that: only the address of the object is the address of the start of the region will it be possible to be selected as a suitable created object. However, as discussed in https://github.com/cplusplus/CWG/issues/98, the intent should be read as that: a suitable created object that would make the program well-formed will have the address of the start of the region.
I think they are completely different meanings. If the intent is the latter, the following change will make the meaning clear
These operations select one of the implicitly-created objects as the suitable created object, and produce a pointer value that points to that object, if that value would result in the program having defined behavior; the address of such a suitable created object is the address of the start of the region of storage.
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
Read the quoted wording in the intro.object section and compare its interpretation with the intent discussed in CWG issue 98. Determine whether the attributive clause is a constraint or a consequence, then confirm agreed wording with the existing discussion. Done means the standard text clearly expresses the intended relationship.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100