17 Jul
2017
17 Jul
'17
10:37 p.m.
On 7/17/2017 6:11 PM, Michel Morin via Boost wrote:
Peter Dimov wrote:
One obvious low-hanging fruit here is moving
from utility to iterator, breaking the utility -> iterator edge; I think this was discussed recently? I posted a related thread last month during the discussion on IteratorTraversalCategory-aware boost::advance (at that time, I didn't know that boost::next/prior is not only for iterators), but I got no response:
[boost] [iterator][utility] Move utility/next_prior.hpp to Iterator module? https://lists.boost.org/Archives/boost/2017/06/236656.php
The change pushed by Andrey was to have iterator not use boost::prior rather than to move boost/next_prior.hpp to iterator.
Regards, Michel