(bunch of ranges) inconsistency about whether `*_view::iterator` has the `class` or `struct` class-key
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
For example, in [range.repeat.view], the repeat_view::iterator member class is declared with the class-key struct. However, in [range.repeat.iterator], repeat_view::iterator is declared with the class-key class.
This is also true for:
The class-keys are consistently struct for:
The others all use class-key class.
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 the class-key declarations in the [range.repeat.view], [range.repeat.iterator], [range.istream], [range.transform], [range.join.with], [range.split], [range.iota], and [range.join] clauses. Determine the project’s preferred convention, update the inconsistent declarations, and verify that all listed iterator declarations use it consistently.
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
- 38/100