Re: [boost] [range] iterator_range operators are too greedy

Jeffrey Lee Hellrung, Jr. <jeffrey.hellrung <at> gmail.com> writes:

Is your type a range?

No.

How does its semantics differ from the operator== above?

I am building an expression template structure to delay operator== evaluation.

Presumably if you want to specifically address boost::iterator_range, then

template< class I > inline bool operator==(my_type, iterator_range<I>);

should be a preferable overload.

Unfortunately it is not. I am getting ambiguity errors. Gennadiy