Overflow Strategy
The strategy for resizing containers.
Include Headers
Changing the capacity of a container can invalidate the iterators of this container.
If no overflow tag is specified, most operations use the default overflow strategy given by DefaultOverflowImplicit or DefaultOverflowExplicit, depending on the kind of operation.
appendConcatenate two containers.
appendValueAppends a value to a container.
assignAssigns one object to another object.
createMakes an object to owner of its content.
insertInserts a sequence into a container.
insertValueInserts a single value into a container.
replaceReplaces a part of a container with another container.
reserveIncreases the capacity.
resizeResizes a container. If the new length exceeds the old length the new elements are filled with copies of value.
No capacity check.
Remarks: The user has to ensure that the container's capacity is large enough.
Limit the contents to current capacity.
Remarks: All entries that exceed the capacity are lost.
Expand as far as needed.
Remarks: The capacity is only changed if the current capacity is not large enough. If the capacity can only be expanded up to a certain ammount, it will be increased as far as possible and the contents are limited to the new capacity.
Note that the capacity will never be shrinked. Use shrinkToFit to resize the capacity down to the current length.
Expand if needed, get precautionary extra space.
Remarks: Whenever the capacity has to be increased, the new capacity is choosen somewhat large than actually needed. This strategy limits the number of capacity changes, so that resizing takes armotized constant time. Use this strategy if the total amount of storage is unkown at first.
The new capacity is computed by computeGenerousCapacity. By default, it is guaranteed not to exceed about tree halfs of the space that is used to store the data. The user can overload computeGenerousCapacity in order to change this behavior.
SeqAn - Sequence Analysis Library - www.seqan.de

Page built @2013/07/11 09:12:39