Need an equivalent of [fs.req.namespace] for chrono LWG 2818
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
Much of the wording in [time] names members of std::chrono by unqualified name, in violation of [contents]p3. But there is also some explicit chrono:: qualification (eg: [tab:time.clock], [time.clock.utc.overview], [time.clock.conv], ...) even when describing entities in the std::chrono namespace.
We should decide if we want an equivalent of [fs.req.namespace], and either add it (and remove the then-redundant chrono:: qualifications throughout), or add all the missing chrono:: qualifications.
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 [time] wording, especially [tab:time.clock], [time.clock.utc.overview], and [time.clock.conv], alongside [contents]p3 and [fs.req.namespace]. The work is done when a consistent namespace-qualification policy is decided and the affected chrono wording is updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100