[range.utility.conv.to] Reuse `container-compatible-range` in `ranges::to`?
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
It seems like:
If
Cdoes not satisfyinput_rangeorconvertible_to<range_reference_t<R>, range_value_t<C>>istrue:
can be replaced with:
If
Cdoes not satisfyinput_rangeorRsatisfycontainer-compatible-range<range_value_t<C>>:
But it doesn't seem necessary.
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
Read the [range.utility.conv.to] wording and compare its constraint with the definition of container-compatible-range in the linked C++ standard clauses. Review the four existing comments for the rationale, then determine whether the proposed substitution is needed and update the draft wording only if the discussion supports a clear resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100