[dcl.init.list] Construction of an `initializer_list` object from a pair of pointers
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
An example in [dcl.init.list] p6 says that "assuming that the implementation can construct an initializer_list object with a pair of pointers". However, it seems unclear in the example itself whether the corresponding constructor can be exposed to users.
Presumably, the additional constructor shouldn't be public since [initializer.list.syn] doesn't show it. Should we clarify this in the example?
(The pointer-pair constructor is public in MSVC STL. But I guess such implementation divergence is just because of some restrictions in MSVC and no LWG issue is needed.)
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 [dcl.init.list] p6 and compare its initializer_list example with [initializer.list.syn]. Clarify in the example whether the pointer-pair constructor is exposed to users, consistent with the synopsis; no test or file is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100