[lib] Phrasing through "inclusion" precludes header imports
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
Wording like https://github.com/cplusplus/draft/blob/3bf6ac52ddd619ae925d32ebb68a90a5bec0c115/source/ranges.tex#L496-L499
suggests that the extra components of <A> defined in <B> are not available when importing A.
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 source/ranges.tex around lines 496-499 and inspect how the wording describes the extra components of one header being defined in another. Clarify whether those components are available when importing the first header, and revise the wording so it does not imply otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100