[func.wrap.ref.class] Redundant description of exposition-only data members
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
Commit 33d767583359e22fed2dcfaa3b27fe90c7dd8329 added the exposition-only data members from the description in paragraph 1.
Now only the second sentence is somewhat relevant.
The paragraph can be simplified to
The type
BoundEntityTypeis capable of storing a pointer to object value or a pointer to function value.
The other requirements on BoundEntityType fall out from the requirements on function_ref in paragraph 2.
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
Search the draft source for [func.wrap.ref.class] and inspect paragraph 1 alongside paragraph 2. Replace the redundant exposition-only-member wording with the proposed BoundEntityType sentence, then verify that the remaining requirements are covered by paragraph 2 and the section still reads coherently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100