[allocator.requirements.general] The meaning of "parameterized in terms of allocators" seems unclear
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 221
- Forks
- 813
- Avg merge
- 16h 4m
- Merged PRs (30d)
- 36
Description
[allocator.requirements.general]/1 says
All of the string types, containers (except
array), string buffers and string streams ([input.output]), andmatch_resultsare parameterized in terms of allocators.
It's not very clear for me whether this sentence imposes some normative requirements, or if it does, what the requirements are, and [syncstream] is not yet covered.
Perhaps it means
If any template in [strings], [containers], [input.output], or [re] is instantiated and any template parameter named
Allocator,Alloc, orSAllocis substituted with a type that does not meet the Cpp17Allocator requirements, the behavior is undefined.
Not sure whether an 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
Start with [allocator.requirements.general]/1 and compare the listed library components with [syncstream]. Review the comment discussion and determine whether the sentence imposes normative requirements or needs clearer wording. Done means the allocator relationship and scope are unambiguous, including whether syncstream is covered.
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
- Needs clarification
- Newbie friendliness
- 25/100