Jonathan Boccara's blog

Inserting several elements into an STL container efficiently

Published 3 weeks ago - 3 Comments

A couple of weeks ago, I had the chance to hear some feedback from Stephan T. Lavavej about the STL learning resource on Fluent C++. This was done during an episode of CppCast (the podcast for C++ developers by C++ developers) where he was a guest.

Stephan said that he found it overall pretty good (yay!) but he had a couple of quibbles about how some of the aspects of the STL were presented. And when you’re lucky enough to have a quibble about the STL coming directly from Stephan T. Lavavej, you want to make the most of this piece of feedback.

Here I want to flesh out one these pieces of advice that he gave. It concerns how to insert several elements into a container.

Inserting several elements into an STL container

In the posts concerning the STL, I use output iterators such as std::back_inserter quite intensely. While such iterators are very handy, it is important to realize that in some cases you don’t want to use them.

And these cases come down to inserting several consecutive elements into an STL container.

The – suboptimal – way to do this by using std::back_inserter is to couple it with std::copy:

Here std::copy successively passes each of the elements in newElements to the output iterator, that adds them to v by calling its push_back method. And this does the job: after the execution of std::copy, all the elements from newElements have been effectively copied into v.

The problem here is that even though before calling std::copy the entire collection of elements is already known (and in particular we know how many of them there are) this piece of information was discarded. Rather, we repeatedly push back into the vector v, just as if we were discovering each time that there was yet another element to append. This potentially causes multiple reallocations of the vector.

Knowing in advance how many elements are going to be added can be exploited by the vector. This lets it minimize the number of reallocations during the operation: it would reallocate once and for all before starting the operation, instead of reallocating several times along the multiple unitary calls to push_back.

So, how can we benefit from this information while inserting into a vector? Just by using the range insertion methods.

At initialization of the vector, use the range constructor:

For appending several new elements to an existing vector:

Note that these methods also exist for the other STL containers, in particular std::set and std::map.

Finally, to replace the entire contents of a vector with newElements:

After the execution of assign, all the previous elements have been replaced by the new ones, regardless of the respective numbers of new and old elements. But for a reason that I didn’t quite understand, the assign method does not exist for associative containers such as std::set and std::map.

Is std::copy useful at all then?

By all means, yes.

In the above case, std::copy was not appropriate because it blindly extended the size of the container. But sometimes, we don’t extend the size of the container, or we can’t know in advance how many elements are to be added.

For instance, if the container already has values, and we want to overwrite them starting at the beginning, we would use std::copy:

Of course, v has to be bigger than newElements for this to work.

Another example is writing into a C array:

And we will see an example of a case where we can’t know in advance how many elements are to be added, when we address stream iterators, in a dedicated post.

Is std::back_inserter useful at all then?

Yes again!

It is typically useful for adding into a container the result of any algorithm that is more complex than std::copy. For example std::copy_if:

Here we don’t directly have a range to insert into the destination container, therefore we can’t use the range insertion methods.

In conclusion, to insert several elements into a container, use the container methods whenever you can. This really ties in with a similar guideline we saw when searching into a container with the STL.

Liked it ? Share this post ! Facebooktwittergoogle_plus    Don't want to miss out ? Follow:   twitterrss