From d940bf6cbe178f96b119eb9fca5af26d867f2d3c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ion=20Gazta=C3=B1aga?= Date: Wed, 4 Feb 2026 15:36:17 +0100 Subject: [PATCH] Remove incorrect allocator management in docs. --- doc/container.qbk | 6 ------ 1 file changed, 6 deletions(-) diff --git a/doc/container.qbk b/doc/container.qbk index a075915..8d5e2ea 100644 --- a/doc/container.qbk +++ b/doc/container.qbk @@ -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]