boost/container
2
0
Fork 0
mirror of https://github.com/boostorg/container.git synced 2026-02-23 03:32:14 +00:00
Code Issues Projects Releases Wiki Activity

Remove incorrect allocator management in docs.

Browse Source
This commit is contained in:
Ion Gaztañaga
2026-02-04 15:36:17 +01:00
parent 2b1c08b010
commit d940bf6cbe
1 changed files with 0 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/container.qbk
View File

@@ -1031,12 +1031,6 @@ offers some workarounds for C++03 compilers to achieve the same allocator guaran
[funcref boost::container::uninitialized_construct_using_allocator uninitialized_construct_using_allocator]
and [funcref boost::container::make_obj_using_allocator make_obj_using_allocator].
Additionally, in [*Boost.Container] containers, if possible, a single allocator is hold to construct
`value_type`s. If the container needs an auxiliary
allocator (e.g. an array allocator used by `deque` or `stable_vector`), that allocator is also
stored in the container and initialized from the user-supplied allocator when the
container is constructed (i.e. it's not constructed on the fly when auxiliary memory is needed).
[endsect]
[section:scoped_allocator Scoped allocators]