[iterator.requirements.general] The constexpr iterator requirements look a bit too terse
Open
Nobody has claimed this yet.
P3-Other
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
From the note, it seems that built-in operators are also considered to be constexpr functions. But the intent doesn't seem deducible from the normative text.
Also, do we want to refer the requirements as Cpp17ConstexprIterator/ContexprIterator?
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 with the [iterator.requirements.general] section, reading the note alongside its normative text. Check how built-in operators are treated as constexpr functions and how the iterator requirements are named. Done means resolving the intended wording and naming questions in the standard draft.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100