[cpp] Explicitly say whether a resulting token sequence is rescanned or not
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
For the resulting sequence that arises from the object-like macro, [cpp.replace.general] p10 explicitly says
The replacement list is then rescanned for more macro names as specified below.
However, we didn't explicitly mention rescan for the resulting sequence replacement list that arises from the function-like macro invocation. This is inconsistent.
[cpp.replace.cpp.subst] p4 implies that we should explicitly mention rescanning for the resulting sequence of a function-like macro invocation.
Otherwise, the argument consists of the results of the expansion of the contained pp-tokens as the replacement list of the current function-like macro before removal of placemarker tokens, rescanning, and further replacement.
Similar to [cpp.replace.general] p10, we should use a similar utterance in [cpp.replace.general] p12.
After the argument substitution has taken place([cpp.subs]), the resulting replacement list is then rescanned for more macro names as specified in [cpp.rescan].
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
Compare [cpp.replace.general] p10 and [cpp.replace.cpp.subst] p4, then locate p12 in [cpp.replace.general]. Update p12 so it explicitly states that the resulting replacement list is rescanned for more macro names after argument substitution; the issue is done when the wording consistently describes rescanning for both macro forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100