id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
6944	Some Range concepts use the incorrect Iterator concept	Andrew Morris <andy@…>	Nathan Ridge	"Due to an omitted namespace specification, the BidirectionalRangeConcept and RandomAccessRangeConcept inside <boost\range\concepts.hpp> use the STL iterator concept checking classes in <boost\concept_check.hpp> instead of the appropriate concepts inside the same file.

This issue was actually noticed in ticket #4355, but a different fix was applied.

The reason that the Range concepts should not use the STL iterator concepts is because the Range concepts only require the relevant traversal concept. ([http://www.boost.org/doc/libs/1_49_0/libs/range/doc/html/range/concepts/overview.html Source])

This example fails on Cygwin g++4.7 and VC2010
{{{
#include <boost/concept_check.hpp>
#include <boost/iterator/iterator_adaptor.hpp>
#include <boost/range/concepts.hpp>
#include <boost/range/iterator_range.hpp>
#include <vector>

typedef std::vector<int>::iterator iter_base;
struct iter : boost::iterator_adaptor<iter, iter_base, int, boost::use_default, int> {}; // will be deduced as random-access traversal but input category
typedef boost::iterator_range<iter> iter_range;

BOOST_CONCEPT_ASSERT(( boost::RandomAccessRangeConcept<iter_range> ));
}}}

I've attached a patch for this issue."	Bugs	closed	To Be Determined	range	Boost 1.49.0	Problem	fixed	range concept iterator