[graph] Boost.Graph 1.95 will be C++17
Dear Boost.Graph community, Jeremy Murphy and I are happy to announce that in two release cycles (Boost release 1.95 in summer 2027) Boost.Graph will be bumped to C++17. This decision follows two polls that did not surface any C++14 user base or demand: Github Poll: https://github.com/boostorg/graph/discussions/490 Reddit Poll: https://www.reddit.com/r/cpp/comments/1tc1v6x/whats_the_highest_c_standard_y... This standard version bump will bring benefits for maintenance, API and dependencies reduction. We will not be able to guarantee backward compatibility with C++14. Please contact us if you are stuck in C++14. The GIthub Discussion lives here: https://github.com/boostorg/graph/discussions/613 Have a wonderful fall season, Best Regards, Arnaud Becheler
On Tue, Sep 29, 2026 at 2:06 AM Arnaud Becheler via Boost < boost@lists.boost.org> wrote:
Jeremy Murphy and I are happy to announce that in two release cycles (Boost release 1.95 in summer 2027) Boost.Graph will be bumped to C++17.
Well, this is very exciting and I am happy to see this work being done!
Thank you Vinnie for your kind words, and thanks for your support and the support of the Alliance to enable these improvements! Bumping to C++17 is “only” context, as there are many things we want to improve with Jeremy Murphy: we were (again) discussing today about parallelization strategies, something that was discussed in the Boost Graph workshop back in May. There is an entire design space here, and bumping to C++17 is part of enabling that strategy. And by 1.95 most of the sanitization efforts should be completed. We are all excited about it! Best wishes, Arnaud Le mar. 29 sept. 2026 à 15:36, Vinnie Falco <vinnie.falco@gmail.com> a écrit :
On Tue, Sep 29, 2026 at 2:06 AM Arnaud Becheler via Boost < boost@lists.boost.org> wrote:
Jeremy Murphy and I are happy to announce that in two release cycles (Boost release 1.95 in summer 2027) Boost.Graph will be bumped to C++17.
Well, this is very exciting and I am happy to see this work being done!
On Tue, Sep 29, 2026 at 7:27 AM Arnaud Becheler <arnaud.becheler@gmail.com> wrote:
Bumping to C++17 is “only” context, as there are many things we want to improve with Jeremy Murphy: we were (again) discussing today about parallelization strategies, something that was discussed in the Boost Graph workshop back in May. There is an entire design space here, and bumping to C++17 is part of enabling that strategy. And by 1.95 most of the sanitization efforts should be completed.
What is the connection of the C++17 Boost.Graph to the authors of the LEWG graph library papers? Thanks
What is the connection of the C++17 Boost.Graph to the authors of the LEWG graph library papers?
I guess you are talking about P3126: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3126r0.pdf The authors are Andrew Lumsdaine (one of the initial authors of BGL) and Phil Ratzloff. Their proposal is based on a design similar to BGL, updated with a modern (C++20) approach. We were interested in exploring ways to collaborate on the proposal, for example, by using BGL as testing grounds for designs (we have a larger user base than they do). Phil was present in Paris for the BGL Workshop, Andrew was the keynote speaker at the end, and we had many interesting questions/discussions. We initially planned to meet at CppCon to work half a day on BGL/std::graph but they couldn't attend in the end. As of today the interaction is stalled because 1) phil priorities shifted a bit, and 2) our priority is to clean/sanitize/stabilize BGL before adding more to it. For example dropping named parameters interfaces. Andrews' teams and collaborators have done lots of work on parallelization and naturally this is interesting for BGL direction. Best wishes, Arnaud
participants (3)
-
Amlal El Mahrouss -
Arnaud Becheler -
Vinnie Falco