How to specify small nested classes: struct/class, private members
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
We have a number of small, nested classes, mainly in the ranges library, which we currently variably specify with class and struct (e.g. outer-iterator, value_type). It might be helpful to pick one class key for all those cases.
A related question is how we order exposition-only members: previously, they used to appear at the end of the class defintion, but the ranges additions have started placing them at the beginning. We should discuss whether we want to mandate any particular style, or if there's value in allowing discretion.
Finally, this is related to the discussion of how to style exposition-only members (#4702).
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
Review the ranges-library examples named in the issue, including outer-iterator and value_type, and compare the related discussion in #4702. Determine whether the draft should standardize class versus struct and the placement of exposition-only members; done means a settled style decision documented for these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100