Re: [boost] Is Boost.Range broken?

Subject: Re: [boost] Is Boost.Range broken?
From: David Abrahams (dave_at_[hidden])
Date: 2008-11-22 13:43:13

on Sat Nov 22 2008, "Pete Bartlett" <pete-AT-pcbartlett.com> wrote:

>
> Thinking of two versions, another point to consider is the existence of
> sub_range.
>
> Whilst I can see that it seems fairly natural for iterator_range<iterator_t>
> to have iterator-like behaviour, what about when it is phrased as
> sub_range<container_t> ? At the moment this is also iterator-like but if you
> were working from intuition rather than from docs, users could also easily
> guess it is container-like.

Not I; I don't expect the elements to be copied.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com