STL: Consider static_asserting when allocators aren't self-rebindable
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
The Standard requires allocators to be rebindable. In particular, rebinding an allocator for X elements to Y elements, and back to X elements, should produce the original allocator type.
User-provided allocators sometimes fail to meet this requirement; deriving from std::allocator improperly is a common cause. We could easily static_assert if we detect that the self-rebinding requirement hasn't been satisfied.
Contributor guide
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 by tracing allocator rebinding in the STL implementation and inspecting existing allocator tests. Confirm how the self-rebinding requirement can be detected for user-provided allocators; done means an appropriate compile-time diagnostic is added without breaking conforming allocators.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100