- Boost - lists.boost.org

Forking Asio
by Vinnie Falco 26 Aug '25

26 Aug '25

I would like to measure the interest in a fork of Asio, proposed as a Boost library for review. Currently, Boost.Asio (and the standalone version Asio) is developed and maintained by Christopher Kohlhoff. Unfortunately he has a well-earned reputation for being unresponsive to emails and GitHub issues. For example: https://github.com/chriskohlhoff/asio/pull/904 I believe that Asio is Boost's most valuable asset, because "the C++ Standard cannot connect to the Internet." Every other language has portable networking built-in except for C++. Asio is the industry standard and the gold standard for portable networking, yet it is falling behind due to its lack of evolution. A major component of my revitalization plan for Boost is to promote Asio and build many great things on top of it. For example, clients and servers which speak MCP ("Model Context Protocol"), empowering users to easily connect and talk to AI endpoints (Large Language Models) using REST and JSON. Learn more about MCP here: https://www.pulsemcp.com/ In discussions with our staff engineers, there is a movement to propose a Boost.Crypt library with cryptographic primitives as an alternative to OpenSSL, with the goal of modern interfaces which eliminate broad categories of undefined behavior and usage errors which lead to vulnerabilities. Yet if Asio cannot adopt support for alternatives to OpenSSL we cannot evolve. The fork of Asio is just in the idea stage, no work has been done yet, and it is all open to debate and design. My thinking of how the fork would work goes like this: 1. C++ Alliance allocates dedicated staff to maintain the fork 2. Stakeholders come together, on the mailing list and through GItHub issues, to determine what directions we might like to explore or move towards 3. Dedicated staff implement the work and provide support for stakeholders 4. Changes in Asio would be adopted on an as-needed basis The first order of business would be to go through all of the GitHub issues in Asio and address them one by one. What do you think?

23 100

(no subject)
by amlalelmahrouss＠icloud.com 26 Aug '25

26 Aug '25

Hi my name is Amlal El Mahrouss and I'm interested in joining this community.

2 1

[release] Boost 1.89.0 Release Candidate 1 is available
by Marshall Clow 25 Aug '25

25 Aug '25

The first release candidates for the 1.89.0 release are now available at: <https://archives.boost.io/release/1.89.0/source/> The SHA256 checksums are as follows: d8b0c1d593d68fe359616aa2fae4b3e258ca1f90ed57eb46c5494c29cdd1d49d boost_1_89_0_rc1.7z 9de758db755e8330a01d995b0a24d09798048400ac25c03fc5ea9be364b13c93 boost_1_89_0_rc1.tar.gz 85a33fa22621b4f314f8e85e1a5e2a9363d22e4f4992925d4bb3bc631b5a0c7a boost_1_89_0_rc1.tar.bz2 77bee48e32cabab96a3fd2589ec3ab9a17798d330220fdd8bde6ff5611b4ccde boost_1_89_0_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release managers

10 21

Boost 1.90.0 Release Notes
by Sam Darwin 21 Aug '25

21 Aug '25

Boost 1.90.0 should be able to use the new process for Release Notes. This is already enabled in the code. - Create a release notes file boost_1_90_0.adoc at https://github.com/boostorg/website-v2-docs/tree/develop/release-notes/boos… . PRs go to the 'develop' branch. - Admins merge to the master branch of website-v2-docs once a week. - Github Actions automatically uploads that to s3. /release-notes/master/boost_1_90_0.adoc - website-v2 versions/releases.py will discover the adoc. If that file exists it takes precedence over the previous methods. Let's be sure a file is there during the beta release.

1 0

[Release] The master branch is now open
by Marshall Clow 15 Aug '25

15 Aug '25

Thank to everyone for their patience. The next release cycle will begin in late October — The release managers

1 0

[release] Boost 1.89.0
by Marshall Clow 15 Aug '25

15 Aug '25

Release 1.89.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. The release contains one new library: * Bloom: Bloom filters, from Joaquín M López Muñoz. as well as numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.89.0> You can also download directly from: <https://archives.boost.io/release/1.89.0/source/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. -- The Boost Release Team Marshall Clow, Glen Fernandes, Ion Ion Gaztañaga

3 3

Updated Release Links
by Robert Beeston 14 Aug '25

14 Aug '25

Good day, There were some issues with the release links, the corrected ones are below: For details, including download links, see https://www.boost.org/releases/1.89.0/ You can also download directly from: https://archives.boost.io/release/1.89.0/source To install this release on your system, see http://www.boost.org/doc/user-guide/getting-started.html *Rob Beeston* Creative Director C++ Alliance cppalliance.org

1 0

Release Report for v1.89
by Robert Beeston 14 Aug '25

14 Aug '25

Here is the link for the 1.89 Release Report: https://downloads.cppalliance.org/reports/boost_1_89_0_release_report.pdf Please let us know if you have suggestions for future reports! *Rob Beeston* Creative Director C++ Alliance cppalliance.org

1 0

Why no "w != NULL" assertion before boost/intrusive/rbtree_algorithms.hpp:511 like before the line 476?
by achinkoff＠gmail.com 12 Aug '25

12 Aug '25

Boost version: latest release file: boost/intrusive/rbtree_algorithms.hpp function: rebalance_after_erasure_restore_invariants in this if-branch ``` if(x == x_parent_left){ //x is left child ``` there is "w != NULL" assertion before variable 'w' access: ``` BOOST_INTRUSIVE_INVARIANT_ASSERT(w); if(NodeTraits::get_color(w) == NodeTraits::red()){ ``` but in else-branch there is no same assertion before variable 'w' access: ``` if(NodeTraits::get_color(w) == NodeTraits::red()){ ``` Why? Are there no assertion in else-branch intentionally due to the rbtree structure itself? Thanks.

2 1

[release] Master branch is now closed for the release
by Marshall Clow 07 Aug '25

07 Aug '25

Master is closed for all changes. See the release schedule at http://www.boost.org/calendar — The release managers

1 0