transform_iterator end iterator with non-default-constructible unary function

Open
#57 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating transform_iterator and its end-iterator construction in the Boost.Iterator module. Inspect how the transformation function is stored and why an end iterator requires another copy, then determine whether the end iterator can be created without that requirement. Done means non-default-constructible unary functions work without constructing or copying a second function.

Written by the indexing model from the issue text.

Description

Currently one have to construct/copy a second copy of transformation function for an end iterator what is unwanted and seems to be omission of the library design. For example, Boost.Range solves it via wrapping user functor with optional, unfortunately.

Dominant language
C++
Stars
23
Forks
70
PR merge metrics
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.