Re: [boost] Is Boost.Range broken?

Subject: Re: [boost] Is Boost.Range broken?
From: Mathias Gaunard (mathias.gaunard_at_[hidden])
Date: 2008-11-22 12:05:03

Dave Handley wrote:

> This is the crux of the issue.  What is an iterator_range trying to be.  
> If it is supposed to be nothing more than a glorified pair of iterators, 
> then so be it.  Allow singular ranges, but don't assert on them.

What's wrong with asserting on them?
Working with singular ranges is always a bug, and iterator_range seems 
to try to help you identify those.

(I'm not too sure what singular means, I'm assuming that singular ranges 
are ranges which are not properly initialized, i.e. their iterators are 
not the results of begin ir end on a valid sequence or incrementations 
on non-past-the-end said iterators).