Re: [boost] [Range] make range_const/mutable_iterator<C>::type non-existent if C is non-range

Arno Schödl skrev:

...

...

Any chance to get this adopted? It seems like a reasonable problem to solve. Neil, what other solutions did you think about?

Another question: is your fix widely portable?

Thorsten,

is it o.k. if I add these Boost.Range changes to my "partition_point" library, so it will be reviewed and adopted as a package? I'd put lazy_typedef into boost::detail::range.

I don't see why not. As for the portability, I guess we can test that on trunk. I'll see if I can get some time to do this... -Thorsten