Daniel James wrote:
On 2 June 2014 22:04, Peter Dimov <lists@pdimov.com> wrote:
boost/iterator.hpp can be moved to core in all its former glory (and probably replaced by a one-liner, using std::iterator.)
Or other libraries could be changed to use std::iterator. Is it worth adding an obsolete header to core?
Moving it is the safer choice; if it turns out that we do need to workaround some uses of std::iterator after all, the changes will be isolated to a single place. But either way is fine with me. Here's the report on boost/iterator.hpp, if we choose the second option: Inclusion report for <boost/iterator.hpp> (in module iterator): from circular_buffer: <boost/circular_buffer/details.hpp> from concept_check: <boost/concept_archetype.hpp> <boost/concept_check.hpp> from filesystem: <boost/filesystem/operations.hpp> from geometry: <boost/geometry/geometries/adapted/boost_polygon/hole_iterator.hpp> <boost/geometry/iterators/base.hpp> <boost/geometry/iterators/closing_iterator.hpp> <boost/geometry/iterators/ever_circling_iterator.hpp> <boost/geometry/views/detail/points_view.hpp> from graph: <boost/graph/adjacency_matrix.hpp> <boost/graph/stanford_graph.hpp> <boost/graph/vector_as_graph.hpp> from multi_array: <boost/multi_array/algorithm.hpp> from spirit: <boost/spirit/home/classic/iterator/multi_pass.hpp> <boost/spirit/home/support/iterators/detail/multi_pass.hpp> from unordered: <boost/unordered/detail/buckets.hpp> from utility: <boost/operators.hpp>