Robert Jacques wrote:
On Thu, 04 Mar 2010 18:22:55 -0500, Andrei Alexandrescu
<[email protected]> wrote:
[snip]
I like this idea. I've gotten used to using template constraints and
ranges when coding which matches this strategy naturally. A lot of the
capabilities seem to match ranges, but why did you use different names
for some of them?
removeBack : popBack
removeFront: popFront
pushBack : put
pushFront : putFront?
It's intentional. You don't want to use a container as a range by mistake.
Andrei