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

Arno Schödl skrev:

...

...

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...

partition_point library will test this for its use cases, which covers the relevant ones:

- use as return value, - use as parameter, - overload disambiguation on it.

Ok, so if it works as portable as Boost.Range, then we can add it to trunk and then it will be part of 1.39. -Thorsten