Re: [boost] Is Boost.Range broken?

Subject: Re: [boost] Is Boost.Range broken?
From: David Abrahams (dave_at_[hidden])
Date: 2008-11-23 01:37:11

on Sat Nov 22 2008, Mathias Gaunard <mathias.gaunard-AT-ens-lyon.org> wrote:

> iterator_range (which is nothing more than a fancy std::pair, I never
> found the use of it myself)

It's a bit less redundant to write the type name, since both members of
the pair have to be the same, and it has a little more communicative power,
since after all pair<Iter,Iter> doesn't have to represent a range; it
has only been retroactively adapted to model Range when p.second is
reachable from p.first.

So, not completely useless, IMO.

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