If I use .reserve(items) on a vector, the vector will allocate enough memory for my guess of the number of items that I'll need.
If I later on use .clear(), will that just clear the vector or save my earlier defined reserve?
thanks.
If I use .reserve(items) on a vector, the vector will allocate enough memory for my guess of the number of items that I'll need.
If I later on use .clear(), will that just clear the vector or save my earlier defined reserve?
thanks.
It will not affect the underlying buffer size. Which is why you have to use tricks like this to actually get rid of the buffer or make it smaller.
It will probably not release the reserved memory although I don't think the behaviour is specified in the standard.
EDIT: Ok, just checked and the standard only says that the post-condition is that size() == 0
although I haven't come across a vector
implementation that doesn't hold on to the reserved memory.
No it won't. Try it out by calling vector::capacity()
.
Further evidence of this is the appearance of shrink_to_fit
. The standard's working draft mentions:
Remarks: shrink_to_fit is a non-binding request to reduce capacity() to size(). [ Note: The request is non-binding to allow latitude for implementation-specific optimizations. —end note ]
No, it won't set reserve() to 0. Calling clear() calls the destructors of each element and removes them from the vector, leaving the container with size of 0, but the capacity remains unchanged.
std::vector<T>::clear()
only affects the size, not the capacity. For resetting the capacity, use the swap trick:
std::vector<int> v1;
// somehow increase capacity
std::vector<int>().swap(v1);