8 Nov
2012
8 Nov
'12
2:48 p.m.
On 08/11/12 14:53, Jeffrey Lee Hellrung, Jr. wrote:
Replacing all overalods of operator== by something like
template<class A0, class A1> typename enable_if< mpl::or_< is_base_of<iterator_range_**base, A0>, is_base_of<iterator_range_**base, A1> > , bool
::type operator==(A0 const& a0, A1 const& a1) { return boost::equal(a0, a1); }
should allow to fix the bug above.
Though an improvement, that's still not very constrained and I doubt it will address Gennadiy's issue.
It would be his responsability to make it so that any additional operator== overload he is a better match...