cplusplus / cplusplus/draft

Index of library names has cbegin(const C&) and cend(const C&)

Open
#5,895 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TeX
Stars
221
Forks
813
Avg merge
16h 4m
Merged PRs (30d)
36

Description

Those are not names.

image

Maybe they should be grouped with the other cbegin and cend names, with "range access" or something as the description. This applies to cbegin(const C&) and cend(const C&) and crbegin(const C&) and crend(const C&).

Also, the first entry in that list (page 1116) is ranges::cbegin which is not at all clear from the index. The discussion in #5831 suggests it should be indexed as cbegin|ranges instead. This applies to all the functions in [range.access], namely ranges::begin, ranges::end, ranges::cbegin, ranges::cend, ranges::rbegin, ranges::rend, ranges::crbegin, ranges::crend, ranges::size, ranges::ssize, ranges::empty, ranges::data, and ranges::cdata.

Combining both suggestions:

cbegin
    basic_stacktrace, 584
    basic_string, 840
    basic_string_view, 823
    containers, 864
    range access, 1105
    ranges, 1116
    tzdb_list, 1528
    unordered associative containers

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the source that generates the library-name index and compare the requested naming with the discussion in #5831. Update the cbegin/cend/crbegin/crend entries and the [range.access] entries so their grouping and ranges labeling match the issue; done means the generated index no longer presents signatures as names and identifies the ranges functions clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, tex
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.