Skip to content

Conversation

@mhoemmen
Copy link
Collaborator

Update non-wording sections

  • Explain reduce_into and transform_reduce_into
  • Show different designs for specifying an identity value
  • Fix grammar and wording

This incorporates design discussions in #31 .

This PR supersedes PR #35. The idea is to put the PR's branch in the main repository, so that other coauthors can push to it.

@rarutyun @akukanov

mhoemmen added 15 commits July 16, 2025 17:47
* Explain that `transform_reduce_into` would include both
  unary and binary versions.

* Discuss output range vs. output single iterator
  and conclude that we want the former.

* Discuss output iterator category in more detail.
* Add `sum_into`, `product_into`, and `dot_into`

* Update P2902 reference to R2

* Update P3179 status throughout (adopted for C++26)
Spell out that for "`_into`" algorithms,
the output range is a nonempty `sized_range` + `forward_range`.
Explain why and discuss alternatives.
Start expressing our 2025/09/10 design discussion about
specifying the identity for reductions and scans.
The new Summary subjection of
"Specifying an identity for reductions and scans"
expresses the result of our discussion.
@akukanov akukanov marked this pull request as ready for review October 16, 2025 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants