P1673: Follow-on to #360
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 29
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
The following P1673 issues were deferred from #360.
- Rename
idx_abs_maxtovector_idx_abs_max. - Hoist
ExecutionPolicywording 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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100