[coro.generator.promise] Ambigous specification of A in p17
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
The [coro.generator.promise] p17 defines A as follows:
Let
Abe
Allocator, if it is notvoid,Allocfor the overloads with a template parameterAlloc, orallocator<void>otherwise
However, it is possible that the conditions for both of the first bullets will be satisfied. In this case, the first bullet should be applied - the required expression imposes convertibility.
Proposed resolution:
Modify 17.1 by adding "otherwise" after coma in 17.
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
Review [coro.generator.promise] p17 and the proposed resolution in issue #5938. Locate the draft text for 17.1 and confirm the ambiguity when both Allocator and Alloc apply. Done when the wording clearly prioritizes the first bullet and includes the proposed “otherwise” clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100