[expos.only.entity] Should we use `iter-value-type` in more places?
Open
Nobody has claimed this yet.
P3-Other
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
The iterator_traits<I>::value_type pattern seems to be quite common in the standard library (for non-ranges utilities). Should we reuse the iter-value-type alias for short?
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 reviewing the issue's comparison between iterator_traits::value_type and the iter-value-type alias, then inspect the standard-library non-ranges utilities where the pattern appears. Done means reaching and documenting a decision about whether the alias should be reused in additional places; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100