P1673: Follow-on to #360

Open
#364 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
documentation

Research direction

Start by reading issue #360 and PR #350, then inspect the P1673 proposal text referenced by this follow-on. Review each deferred checklist item and confirm the relevant wording or naming decisions; done means every item has a documented resolution, including the LWG question.

Written by the indexing model from the issue text.

Description

The following P1673 issues were deferred from #360.

  • Rename idx_abs_max to vector_idx_abs_max.
  • Hoist ExecutionPolicy wording to apply to both this and the parallel algorithms.
  • As a follow-on to PR #350, can we move from Cpp17* named requirements to concepts?
  • Ask LWG if we really need the synopsis. It almost doubles the size of the proposal.
Dominant language
HTML
Stars
29
Forks
26
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 ORNL/cpp-proposals-pub

All issues in ORNL/cpp-proposals-pub

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.