boost/container
2
0
Fork 0
mirror of https://github.com/boostorg/container.git synced 2026-01-19 04:02:17 +00:00
Code Issues Projects Releases Wiki Activity

Fix class invariant comment. In this implementation default constructed deque make no allocation so in that case start and finish are singular iterators.

Browse Source
This commit is contained in:
Ion Gaztañaga
2025-07-30 23:57:26 +02:00
parent ba82a1da7d
commit e680bd79a2
2 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/container.qbk
View File

@@ -481,7 +481,7 @@ inserted predominantly on one extreme (e.g. pushed at one extreme and popped fro
To avoid unbounded memory waste, Boost.Container's `devector` uses a different strategy:
* If elements are inserted near a extreme and there is free space on that extreme, the insertion is performed
without any additional data movement (only the elements between the insertion point and the extreme are moved.
without any additional data movement (only the elements between the insertion point and the extreme are moved).
* If elements are inserted near one extreme and the free space on that extreme is exhausted, all existing elements
are relocated (moved) to the center of the internal memory buffer. This makes room in the exhausted extreme
@@ -492,7 +492,7 @@ To avoid unbounded memory waste, Boost.Container's `devector` uses a different s
relocations must be limited ('relocation limit') and a reallocation (allocation of a new memory buffer) will be
performed if the load-factor of the container defined as (size()/length_of_buffer) surpasses the relocation limit (see
Lars Greger Nordland Hagen's [@http://larshagencpp.github.io/blog/2016/05/22/devector "Double-ended vector - is it useful?"]
article for more details.
article for more details).
* This approach offers a reasonable balance between a reasonable memory overhead and performance.