Re: [boost] Is Boost.Range broken?

There's no reason that they both have to be in boost. Boost range should let you use your own range class.

And you're absolutely right. Having said that, it's not inconceivable that others may have been relying on the same behavour. That's one of the things this discussion was about.