[basic.types.general] Talk about "program points", not "certain contexts"
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
Especially after https://cplusplus.github.io/CWG/issues/3065.html, we use the wishy-washy language "in certain contexts" in https://eel.is/c++draft/basic.types.general#5:
A class type in certain contexts, an enumeration type in certain contexts ([dcl.enum]), or an array of unknown bound or of incomplete element type, is an incompletely-defined object type. [...]
It would be better to say "at certain program points" now that we have proper language to express this (I believe program points were recently introduced with C++26 Reflection).
I've floated the idea during yesterday's CWG telecon and it sounded like this may be doable editorially.
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 at basic.types.general paragraph 5, linked in the issue, and review the surrounding terminology for program points introduced by C++26 Reflection. Update the editorial wording as appropriate, then build or render the draft to verify the section formatting and references.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 65/100