29 Jul
2014
29 Jul
'14
4:12 p.m.
On Tuesday 29 July 2014 08:31:55 Eric Niebler wrote:
Can you point me to the operator overload in Boost.Range that is causing this problem? The longer-term fix is to be smarter there.
All operators for iterator_range are potential sources of the problem, see boost/range/iterator_range_core.hpp:537 and below. In this particular case it was operator<. I've created a ticket [1] suggesting to move all Boost.Range components into its own namespace. [1] https://svn.boost.org/trac/boost/ticket/10269