[range.access] Show CPOs in [iterators] synposis?
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
We have mandated that <ranges> includes <iterator>, and that CPOs in [range.access] are also available by including <iterator>. As a result, it's sufficient enough to mention these CPOs in [iterator.synopsis], and doing so may encourage users to include less headers while only these CPOs are wanted.
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 by comparing the [range.access] and [iterator.synopsis] clauses linked in the issue, checking how the CPOs are currently presented. The change is complete when the relevant CPOs are also mentioned in [iterator.synopsis] without conflicting with the stated header-availability rules.
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
- Mostly clear
- Newbie friendliness
- 35/100