Update for compatibility with C++20 iterator concepts

Open
#89 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
tooling

Research direction

Start by reviewing Boost.Iterator's iterator-category deduction and the C++20 rules described in this issue, then inspect the linked example in issue 88. Compare the current C++03-based behavior with C++20 and earlier standards. Done means C++20 and later use the newer rules while C++17 and older retain the existing rules.

Written by the indexing model from the issue text.

Description

In C++20, forward iterators (and more advanced) no longer require the iterator reference type to be an actual reference. Instead, it is required that a reference can be formed to the reference type.

Since Boost.Iterator iterators still define their categories using C++03 rules, some iterators receive unnecessarily strict categories in terms of C++20. Here is one example.

Perhaps, we should use C++20 rules for deducing iterator categories in C++20 and later and the current rules in C++17 and older.

Dominant language
C++
Stars
23
Forks
70
No merged PRs in 30d

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.

More from boostorg/iterator

All issues in boostorg/iterator

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.