pop_front() and pop_back() docs missing

[Olaf van der Spek <olafvdspek@…>]

These iterator_range functions appear to be undocumented.

[Dave Abrahams]

OK, but the names (at least the ones that get documented) should be changed to drop_front and drop_back. pop_xxx implies the element is getting destroyed.

[Neil Groves]

That's a great suggestion. I used the names from the Alexandrescu work, but this is better.

[Olaf van der Spek <ml@…>]

I like pop_ better, especially as existing code is already using it. The type already indicates it's not actually destroying elements. Just like pop_back() for a vector<T*>.

[Neil Groves]

I much prefer drop_front and drop_back as it avoids accidentally modifying containers. While I appreciate the frustration of having to modify your code it is a small change to functions that were not documented.

I've modified all of my code that uses these functions in the space of half an hour. I hope that the increased work that you incur is small too.

I've renamed the functions and added tests for these.

[Olaf van der Spek <ml@…>]

I'll survive, do the required #ifdef's based on BOOST_VERSION probably won't be pretty.

[Olaf van der Spek <ml@…>]

though*