memory: Add allocator_traits and deprecate old specialized version #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The containers use
default_allocator_traits
as well as theallocate()
anddeallocate()
functions of its allocator directly. Although this approach was sufficient to relax several restrictions, it is inconsistent and does not reflect the desired behavior specified in the C++ standard. Introduceallocator_traits<Allocator>
which resolves this problem and provide a standardized access the allocators. Deprecate the olddefault_allocator_traits
which do not model the interface correctly. Note that the current implementation is oversimplified and always uses the fallback solution rather than detecting the capabilities ofAllocator
. Furthermore, this fixes an attribute issue in the recently introducedget_allocator()
functions (see #56).