- Boost-announce - lists.boost.org

[review] The review of boost::container::hub starts! April 16 - April 26
by Ion Gaztañaga 15 Apr '26

15 Apr '26

Dear users and members of Boost, I'm proud to announce that the formal review of Joaquín M López Muñoz's boost::container::hub container, for inclusion in the Boost.Container library, starts today ( in my timezone ;-) ), April 16, and runs through April 26. It may be downloaded from https://github.com/joaquintides/hub and the documentation may be found here: https://github.com/joaquintides/hub/blob/develop/README.md Anyone is welcome to post a review and/or take part in subsequent discussions (see below for review guidelines). Introduction ------------ boost::container::hub is a sequence container with O(1) insertion and erasure and element stability: pointers/iterators to an element remain valid as long as the element is not erased. boost::container::hub is very similar but not entirely equivalent to C++26 std::hive (hence the different naming, consult the section "Comparison with std::hive", for details): https://github.com/joaquintides/hub/blob/develop/README.md#comparison-with-… boost::container::hub has excellent performance, you can see some benchmarks here: https://github.com/joaquintides/hub/blob/develop/README.md#performance Basic example: #include <boost/container/hub.hpp> #include <cassert> int main() { boost::container::hub<int> h; // Insert some elements and keep an iterator to one of them for(int i = 0; i < 100; ++i) h.insert(i); auto it = h.insert(100); for(int i = 101; i < 200; ++i) h.insert(i); // Erase some of the elements erase_if(h, [](int x) { return x % 2 != 0;}); assert(*it = 100); // iterator still valid // Insert many more elements for(int i = 200; i < 10000; ++i) h.insert(i); assert(*it = 100); // iterator still valid } An important tradeoff when using boost::container::hub is the fact that the user can't control the position where a new element will be inserted: boost::container::hub reuses the memory addresses of previously erased elements to maximize performance and keep the data structure as compact as possible. The primary use case for boost::container::hub is in high-performance scenarios where elements are created and destroyed frequently, insertion order is not relevant and pointer/iterator stability is required: game entity systems, particle simulation, HFT... For more information, see the Tutorial section: https://github.com/joaquintides/hub/blob/develop/README.md#tutorial Review guidelines ----------------- Please provide in your review whatever information you think is valuable to understand your final choice of ACCEPT or REJECT including Fit as a Boost component. Please be explicit about your decision. Some other questions you might want to consider answering: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? (Note that, if accepted, final documentation will be included in Boost.Container docs, so please review the content, not the format) - What is your evaluation of its potential usefulness? - Did you try to use the container? With which compiler(s)? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? More information about the Boost Formal Review Process can be found here: http://www.boost.org/community/reviews.html Kind regards, Ion Gaztañaga, Review manager

1 0

[review] [hub] boost::container::hub review starts on April 16
by Ion Gaztañaga 04 Apr '26

04 Apr '26

Dear Boost community, The formal review of Joaquín M. López Muñoz's boost::container::hub container is scheduled for April 16 - April 26. Hub is a nearly drop-in replacement of C++26 std::hive that has excellent performance. https://github.com/joaquintides/hub/blob/develop/README.md#performance The codebase is fairly small (single 1800-LOC header), and due to the subject matter, it is proposed to be part of Boost.Container rather than as a separate library. You can find code and documentation here: https://github.com/joaquintides/hub Best, Ion

1 0

Farewell to Wowbagger - End of an Era for boost.org
by René Ferdinand Rivera Morell 18 Mar '26

18 Mar '26

Dear Boost developers and community, On behalf of the Fiscal Sponsorship Committee, I'm writing today with a mix of gratitude and nostalgia to share some news: after 15 years of faithful, but rocky, service, wowbagger - the server that hosted boost.org, lists.boost.org, and subversion - is being mothballed. For many of us, it was simply there - one of those invisible pillars that kept our community connected and our work accessible to the world. It deserves a proper send-off. What happened: Rackspace recently notified customers that pricing on their legacy cloud platform is increasing significantly - effectively doubling - as they wind down the previous generation of cloud servers in favor of their next-generation platform. Migration is not automatic. After consulting with Marshall and others, we made the decision to terminate our Rackspace instances rather than absorb the increased costs or undertake a manual migration to a platform we no longer need. What this means: We (i.e. Sam Darwin) have stopped wowbagger for now. File-level backups and disk snapshots are in hand. After another week, the server will be deleted. This is purely a housekeeping matter - boost.org and lists.boost.org are already running on new, upgraded hardware and have been for some time. The old machine had been kept around as a reference for comparing web pages between the old and new sites, but the Rackspace pricing change simply accelerates a retirement that was already overdue. Nothing changes for us. The website and mailing lists continue to operate normally on their new home. Still, we wanted to take a moment to honor wowbagger's long run. 15 years is a remarkable tenure for any server, and this one carried the public face of Boost for all of that time. To everyone who set it up, maintained it, patched it at odd hours, and kept it humming along - thank you. Your work mattered more than most people ever realized. Rest well, wowbagger. You've earned it. Warm regards, Boost Fiscal Sponsorship Committee (Ion Gaztañaga, Joaquín M López Muñoz, René Ferdinand Rivera Morell)

1 0

Boost 1.90.1 beta 1 released
by Marshall Clow 11 Mar '26

11 Mar '26

Boost release 1.91.0 beta 1 is now available at: https://archives.boost.io/beta/1.91.0.beta1/source/ The SHA256 checksums are: b8e78a226d2c0bd6ad4346254988dc2af15c0ae569d974e4da09e7dd0f338980 boost_1_91_0_b1.zip d1eb15102b3379bff874894dd0c39d25a85c9c41147a2dd25215602b911125db boost_1_91_0_b1.tar.bz2 866a39f4b6b1591c04bbb7d9c70ed241a794162512df0fa2ef79374b774354a3 boost_1_91_0_b1.7z 1194fb011943b4425cc6e15f3ee7272ae9c8331938c7d1bac8767850463c2e84 boost_1_91_0_b1.tar.gz Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- The release managers

1 0

[release] Boost 1.90.0
by Marshall Clow 10 Dec '25

10 Dec '25

Release 1.90.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: * OpenMethod: Open-(multi-)methods in C++17 and above, from Jean-Louis Leroy. 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.90.0> You can also download directly from: <https://archives.boost.io/release/1.90.0/source/> To install this release on your system, see <https://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 Gaztañaga

1 0

[release] Boost 1.90.0 beta 1 released
by Marshall Clow 13 Nov '25

13 Nov '25

Boost release 1.90.0 beta 1 is now available at: https://archives.boost.io/beta/1.90.0.beta1/source/ The SHA256 checksums are: 8072831c2c54c7e0e99c69e934b5694574565dd435de19a0a43f7bf7dabad71b boost_1_90_0_b1.zip d1754f544e83418c2b5fe18245666830088948cb3629d2b346d56f31c71138e5 boost_1_90_0_b1.tar.bz2 c94235eb00edc732253d3ae8000a489ffc5773f34cd98bd7645d54cb4ae2482a boost_1_90_0_b1.7z 0f55a646eaed4daf110eeec7c2c70e2c7058efa77eef31137248a6e2cf1412da boost_1_90_0_b1.tar.gz Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- The release managers

1 0

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

14 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

1 0

[release] Boost 1.89.0 beta 1 released
by Marshall Clow 17 Jul '25

17 Jul '25

Boost release 1.88.0 beta 1 is now available at: https://archives.boost.io/beta/1.89.0.beta1/source/ The SHA256 checksums are: 9ece9af2b243f90b76f679b278b512b6589c7843e4dd54cffcb719bbc0801998 boost_1_89_0_b1.tar.bz2 bf45af4a58f39c2ec374ef6e70b26859b786ba2ed087bc869d92a2b4de14e0d2 boost_1_89_0_b1.zip f255b4a31558b3fb81be1dc7e8b367fb9997dbe5e71da98a730c681377abffa9 boost_1_89_0_b1.7z 984ee193ddf192795ba635d4c73b2b43e1e596995d7ce5519a3a72fab9bc0b40 boost_1_89_0_b1_rc1.tar.gz Release notes (still need updates): https://original.boost.org/users/history/version_1_89_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

1 0

mailman upgrade
by Sam Darwin 04 Jun '25

04 Jun '25

Hi, As discussed earlier on the developer list, mailman2 is end-of-life and no longer supported. We are planning to upgrade the mailing lists from mailman2 to mailman3. This will be done in-place, importing the previous archives and user list into a mm3 instance hosted at the same URL lists.boost.org. An example staging instance can be viewed at https://lists.preview.boost.org Mailman3 is more complex than Mailman2 with multiple components including "web" and "core". After the upgrade your account should still exist in the core backend, which means you will continue to receive messages and be able to send emails. However, to interact with the web frontend (optional) you must register an account using the same email address at https://lists.boost.org. Registering in the web portal will require setting up a new password, and confirming the email address. Be sure to use your existing email from before. Any previous passwords will not be valid. If you don't create an account in the web UI, your email subscriptions to the lists continue. But you can't yet log in to configure the account. No action is needed right now. Wait until after the upgrade. All previous messages will be imported to the new system. Additionally, the earlier archives in the form of static plain html pages will be available at https://listarchives.boost.org/ The imported lists are Boost, Boost Announce, and Boost Users. Activity on any other lists is remarkably low such as 1-2 emails per year. Please migrate other discussions to Github Issues, Slack, or one of the main mailing lists. Let us know any concerns. Report issues in the github repository cppalliance/boost-mailman. The tentative schedule is Tuesday June 17. Plan on not using the list for one day, or perhaps a few days. Roll back to mailman2 if something unusual is discovered soon after going live. Chat out-of-band in cpplang slack boost channel.

1 0

[boost] [openmethod] Peer review conclusion
by Дмитрий Архипов 28 May '25

28 May '25

Dear Boost community, the formal review of candidate Boost.OpenMethod has taken place between 28th of April and May 7th. I have received 6 reviews in total. Four of the reviews recommended unconditional, and 1 conditional acceptance. One reviewer recommended to reject the library. The reviews came from: - Joaquin M López Muñoz, - Christian Mazakas, - Ruben Perez, - Yannick Le Goc, - Klemens Morgenstern, - Andrzej Krzemienski. Also, several people have given insightful comments but did not provide a review. I would like to thank all of the people who took their time to write reviews or participate in the discussions. Your effort was very important and valuable. The outcome of the review is that Boost.OpenMethod is ACCEPTED with some CONDITIONS. 1. The convenience header <boost/openmethod.hpp> should be changed to not introduce identifiers to the global namespace. Reviewers suggested several alternatives to that: either moving those global entities into an alternative header, or put them into a dedicated namespace which users could use via using namespace. 2. The library should not choose an arbitrary ambiguous overrider. Virtually all reviewers have expressed strong dislike for this behaviour. The default should be an error. More lax overrider selection may be provided as an option. 3. The library's documentation should be improved in several areas: * The concepts used by the documentation should be explained early on and more thoroughly. * The library should not claim to implement N2216, as it diverges from it significantly. Instead it may remark on being inspired by it. * Better explain potential platform-specific limitations of certain use cases (runtime loading of shared libraries) and error conditions. In addition, I want to discuss several criticisms that have been expressed during the review. One is that essentially the library doesn't solve a problem that is worth solving. That is, you never need an open set of types combined with an open set of operations. I believe that 10 years of library's use should mostly dispel such concerns. I personally have also encountered such a situation in my practice. The second criticism is that the flexibility of the library comes with higher chance of programmer error, as some usual safe guards go out the window. I can attest that in "many types, many operations" situations alternative approaches are comparably error-prone. It seems to me that this is largely inherent to the complexity of the problem. My advice to the author is to highlight dangerous situations, so that potential users can better evaluate if the added flexibility is worth it. Thanks to Jean-Louis Leroy for submitting this library to Boost. And thanks again to the reviewers and everyone who provided feedback, who ultimately made this review possible.

1 0