std::max_element requires forward iterator

[boostorg]

std::max_element requires forward iterator

[anadon]

Hello,

I'm getting back to this repo after a month and a half. While it is possible to make a loop in user code, that might not be the right option. Though it may also be correct since a forward iterator may not make sense in a graph since it isn't convertible in a reliable way to a 1D directional structure. I am working on Travis CI stuff right now and have a backlog, but I'll address this when I can. If you would like a faster resolution and feel comfortable doing so, I will welcome you to create a test case and a code fix in a PR.

[morinmorin]

C++20's new overloads of std::max_element would work. But, no need to wait for C++20! We already have boost::range::max_element (or boost::first_max_element in Boost.Algorithm) that works with ForwardTraversal ranges (iterators).

[bkpoon]

I ran into this issue while trying to compile our code using Boost.Graph on macOS with Xcode 11. It looks like Boost.Range did what @morinmorin suggested by replacing std::max_element with boost::first_max_element (boostorg/range@adcb071).

For testing our code, I modified include/boost/graph/bc_clustering.hpp to add the <boost/algorithm/minmax_element.hpp> header, removed the <algorithm> header, and replaced line 136

        = *max_element(edges_iters.first, edges_iters.second, cmp);

with

        = *boost::first_max_element(edges_iters.first, edges_iters.second, cmp);

I'm still testing this on the other platforms and compilers that we support, though. I can submit a pull request if that helps.

[bkpoon]

I made a pull request (#190). There was another file, include/boost/graph/howard_cycle_ratio.hpp, that has the same issue, so I patched that as well.