July 2024 - Boost - lists.boost.org

[release[ Boost 1.86.0 Beta 1 Release Candidate is available
by Marshall Clow 23 Jul '24

23 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: 90be7ebbaf1c81a849791eb0f49d05a9ec7dbd0ec98b974dfe31d44d811e8298 boost_1_86_0_b1_rc1.7z 543ca3b743250a8b24b25c71209cf911c35613910e78a320835c21c053212ef2 boost_1_86_0_b1_rc1.tar.gz 1bf831ed717fa3e01db6c1f104b95f5a6a8d098a4cc9e61fa6eb81969c78645f boost_1_86_0_b1_rc1.tar.bz2 f739f8761bee6006c60a39fd21ed80b7b0a681c9ed448d1ae1bb28d8d8a69659 boost_1_86_0_b1_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

7 13

[Release] Master branch is closed for beta
by Marshall Clow 23 Jul '24

23 Jul '24

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html -- Release managers

3 4

Q2 2024 Transparency Report on Boost C++ Library
by Louis Tatta 22 Jul '24

22 Jul '24

Hello, Louis Tatta here, CEO of The C++ Alliance, Inc, a registered 501(c)(3) non-profit organization dedicated to supporting C++. This is our Q2 2024 transparency report on our charitable work for the Boost C++ Library Collection. The C++ Alliance actively seeks out highly talented and experienced C++ experts, hiring them, often full-time, so they can fully dedicate themselves to open-source projects. Our Staff Engineers maintain existing Boost libraries, develop new ones, and contribute to other Boost projects. We also employ IT experts full-time to maintain and enhance the infrastructure supporting Boost. This includes the legacy web server, the Drone continuous integration servers, deployment scripts for GitHub Actions on Boost repositories, and scripts that publish Boost releases. Additionally, we provide on-demand technical support services for Boost authors and maintainers facing infrastructure-related issues. The Boost Mailing List remains the premier venue for high-quality discussions on Boost libraries and related C++ Standards topics. The C++ Alliance continues to support the mailing lists, upgrading them to the latest Mailman version and developing an optional web-based front-end for browser-based interaction. We also manage the Official C++ Language Slack Workspace ( https://cpp.al/slack) hosting the most popular interactive discussions on Boost libraries. The C++ Alliance sponsors a paid plan to offer full history, video and audio conferencing, collaboration tools, and unlimited document storage for seventeen dedicated Boost library channels and one main Boost discussion channel. Our largest project for Q2 2024 is the ongoing development of the new Boost website. This new site will be a C++ social media portal with rich support for user-generated content and a robust back-end that provides visibility into contributions made on GitHub and the release process. Our goal is to deliver an enhanced user experience that attracts fresh talent to Boost. Notably, the website features hand-drawn graphics by our contract artist, reflecting our commitment to ensuring Boost not only functions well but also looks visually appealing. In Q2 2024 there were a total of zero Boost Formal Reviews. There were two petitions for endorsement for potential Boost candidates: *async_mqtt from Takatoshi Kondo (https://github.com/redboltz/async_mqtt) *multi from Alfredo Correa (https://gitlab.com/correaa/boost-multi) There's another MQTT library in the works proposed on Nov 2023, Async.MQTT5 from Ivica Siladic, Bruno Iljazovic and Korina Simicevic ( https://github.com/mireo/async-mqtt5) There were a total of three messages from the @Boost_Libraries X (formerly Twitter) account, all submitted by C++ Alliance team members. One of them featured artwork from Bob Ostrom, commissioned by us. Posts with visuals are three times more engaging than those with just text. We see the X platform as a vital tool for educating newer generations about the benefits of Boost. A total of $526,000 was spent on Boost-related contributions, broken down thusly (and rounded to the nearest thousand): Staff Engineers Compensation $392,000 Website Software Development $111,000 Server Hosting $23,000 During Q2 2024 we employed a total of 13 individuals to contribute to Boost. Here is a high-level summary of accomplishments: Sam Darwin (Chief Technical Officer) - Summary: Sam Darwin led major projects, overseeing the integration of new features in the Boost infrastructure. He coordinated between teams, ensuring smooth transitions and high-quality deliverables. His leadership was pivotal in the development of the new Boost website and improvements to the mailing list system. - Link: Sam Darwin's Q2 Update <https://cppalliance.org/sam/2024/07/10/SamsQ2Update.html> Dmitry Arkhipov (Staff Engineer) - Summary: Dmitry Arkhipov focused on maintaining and enhancing Boost libraries. He implemented several bug fixes, optimized existing code, and contributed to the development of new libraries. Dmitry also played a significant role in the continuous integration and deployment processes. - Link: Dmitry Arkhipov's Q2 Update <https://cppalliance.org/dmitry/2024/07/12/dmitrys-q2-update.html> Alan de Freitas (Staff Engineer) - Summary: Alan de Freitas worked extensively on the Boost website redesign, particularly on the back-end systems that support user-generated content and GitHub integration. He also contributed to developing new libraries and maintaining existing ones. - Link: Alan de Freitas's Q2 Update <https://cppalliance.org/alan/2024/07/13/AlanQ2Update.html> Christian Mazakas (Staff Engineer) - Summary: Christian Mazakas worked on enhancing Boost’s infrastructure, including optimizing server performance and improving deployment scripts. His contributions were crucial for maintaining the stability and efficiency of the Boost libraries. - Link: Not provided. Krystian Stasiowski (Staff Engineer) - Summary: Krystian Stasiowski focused on developing new features for existing Boost libraries and worked on performance optimizations. His work included contributing to the ongoing development of new libraries and providing technical support to other Boost authors. - Link: Krystian Stasiowski's Q2 Update <https://cppalliance.org/krystian/2024/07/15/KrystiansQ2Update.html> Peter Turcan (Senior Technical Writer) - Summary: Peter Turcan was responsible for creating and updating documentation for Boost libraries. He ensured that all new features and libraries were well-documented, making it easier for users to understand and utilize Boost’s capabilities. - Link: Peter Turcan's Q2 Update <https://cppalliance.org/peter/2024/07/07/PeterTurcan-Q2-2024.html> Matt Borland (Staff Engineer) - Summary: Matt Borland contributed to the development of new libraries and enhancements to existing ones. His focus was on improving library performance and ensuring that the codebase remained robust and reliable. - Link: Matt Borland's Q2 Update <https://cppalliance.org/matt/2024/07/08/Matts2024Q2Update.html> Ruben Perez (Staff Engineer) - Summary: Ruben Perez worked on several infrastructure projects, including server maintenance and optimization. He also contributed to the development and maintenance of Boost libraries, focusing on performance improvements and bug fixes. - Link: Ruben Perez's Q2 Update <https://cppalliance.org/q2_update/2024/07/09/RubenQ2.html> Mohammad Nejati (Staff Engineer) - Summary: Mohammad Nejati was involved in developing new libraries and improving existing ones. He focused on optimizing code and ensuring that Boost libraries were efficient and reliable. His work also included providing technical support to other developers. - Link: Mohammad Nejati's Q2 Update <https://cppalliance.org/mohammad/2024/07/10/MohammadsQ2Update.html> Fernando Pelliccioni (Staff Engineer) - Summary: Fernando Pelliccioni contributed to the ongoing development of the Boost libraries, focusing on implementing new features and optimizing performance. His work was instrumental in ensuring the high quality and reliability of Boost libraries. - Link: Fernando Pelliccioni's Q2 Update <https://cppalliance.org/fernando/2024/07/08/FernandoQ2Update.html> Joaquin M Lopez Munoz (Staff Engineer) - Summary: Joaquin M Lopez Munoz worked on several key projects, including the development of new Boost libraries and enhancements to existing ones. His contributions focused on improving code efficiency and performance. - Link: Joaquin M Lopez Munoz's Q2 Update <https://cppalliance.org/joaquin/2024/07/06/Joaquins2024Q2Update.html> Kenneth Reitz (Staff Engineer) - Summary: Kenneth Reitz focused on developing and maintaining Boost libraries, implementing new features, and optimizing existing code. His work also involved providing technical support and contributing to the Boost website redesign. - Link: Kenneth Reitz's Q2 Update <https://cppalliance.org/kenneth/2024/07/12/KennethQ2Update.html> Braden Ganetsky (Junior Staff Engineer) - Summary: Braden Ganetsky, as a junior engineer, contributed to various Boost library projects. His work included implementing new features, fixing bugs, and assisting with infrastructure maintenance. Braden’s contributions were valuable in supporting the overall development efforts. - Link: Braden Ganetsky's Q2 Update <https://cppalliance.org/braden/2024/07/14/BradenQ2Update.html>

6 8

Modular Boost status..
by René Ferdinand Rivera Morell 21 Jul '24

21 Jul '24

Yesterday I created PRs for each library that introduces the changes to build (and some code) to implement the modular B2 building. I track all the PRs here: <https://github.com/users/grafikrobot/projects/1/views/2> All the library PRs are in Draft status, as we wait for the tool related PRs to get merged. You can read an explanation of the changes here <https://github.com/grafikrobot/boost-b2-modular/blob/b2-modular/README.adoc> (the explanations may differ slightly from current reality). IMPORTANT: The PRs are all "Draft" as I continue to monitor build errors from any CI errors in the PRs. And to address feedback from authors. After the current release the process will go something like this: * I fix any current fallout in draft PRs. * The 1.86 release happens. * The owners merge the tool PRs to develop and master. * I fix any fallout from that. * Authors, and owners, merge library PRs to develop and master. * I fix any fallout from that. * I create subsequent PRs for the global B2 Boost build infrastructure to remove the old non-modular dead code. * The 1.87 release happens. Questions? -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

1 0

[compute] Maintenance status
by Joaquin M López Muñoz 21 Jul '24

21 Jul '24

It was brought to my attention that Boost.Compute seems to be all but abandoned: no updates in three years, more than 100 issues filed, 27 unattended PRs. This is a shame given that the library looks pretty popular based on GH stars and references on Internet. Are there volunteers to take on maintenance of the library? Best, Joaquin M Lopez Munoz

1 0

Should include of quadmath.h in multiprecision/cpp_bin_float.hpp be guarded with ifdef BOOST_MATH_HAS_QUADMATH_H?
by Martin Jambor 19 Jul '24

19 Jul '24

Hello, because of a bug[1] in GCC 13 and earlier versions, the #include of quadmath.h in multiprecision/cpp_bin_float.hpp did not fail even when the header file was not present on the system and compilation succeeded as long as nothing from the header file was actually needed. The bug has been fixed in GCC 14 which all of a sudden leads to new build requirements and failures such as [2]. Examining this build failure, I noticed that in math/special_functions/fpclassify.hpp (which is indirectly included from multiprecision/cpp_bin_float.hpp) the existence of the header file is specifically tested and macro BOOST_MATH_HAS_QUADMATH_H is defined or not accordingly. So I wanted to ask the question in the $subject. Could, or perhaps even should the include (together with its uses introduced in commit 4911125248bd) be guarded also by BOOST_MATH_HAS_QUADMATH_H and not just by BOOST_HAS_FLOAT128? Thank you, Martin [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80753 [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1225861#c7

2 1

Boost Foundation, Boost, and the Beman Project
by Peter Dimov 19 Jul '24

19 Jul '24

Hi all, I recently brought up (by e-mail) the subject of the relationship between the Boost Foundation and the Beman Project before the BF board. I expressed the opinion that, since the Boost Foundation's primary purpose is to support Boost, the Beman Project should eventually have its own backing entity (foundation/nonprofit), instead of the existing Boost Foundation supporting both. David Sankel responded, quoted Boost Foundation's mission statement: "The Boost Foundation’s broad C++ mission is: (a) development of high quality, expert reviewed, legally unencumbered, open-source libraries, (b) inspiring standard enhancements, and (c) advancing and disseminating software development best practices. It does this by fostering community engagement, nurturing leaders, providing necessary financial/legal support, and making directional decisions in the event of Boost community deadlock." and helpfully pointed out that it very much doesn't say that supporting Boost is the primary purpose of the Foundation. And indeed, if one pays attention to the above, one would notice that Boost only appears once, at the end, somewhat incidentally, and as an afterthought. Unsurprisingly, I disagree. I think that the primary purpose of an entity named "the Boost Foundation" should be to support Boost, and if it currently isn't, something not quite right. At the moment I'm not proposing anything yet; this is purely informative. But no matter how I look at it, I see a pretty fundamental difference of opinion, which we'll need to deal with at some point.

12 32

Re: [boost] Boost Digest, Vol 7285, Issue 2
by Adam Getchell 19 Jul '24

19 Jul '24

> Date: Wed, 17 Jul 2024 13:38:58 -0700 > From: Vinnie Falco <vinnie.falco(a)gmail.com> > To: boost(a)lists.boost.org > Cc: Robert Ramey <ramey(a)rrsd.com> > Subject: Re: [boost] New Logo Discussion > Message-ID: > <CA+EzHGfmxMdhD04BCYz4Rvzk663KejBa+8QDF1fX84ZW1A3Ytg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Wed, Jul 17, 2024 at 12:42?PM Robert Ramey via Boost < > boost(a)lists.boost.org> wrote: > >> FWIW - I much prefer the current logo which was developed by community >> inclusive process with many submissions and designs. >> > > Thanks. Upon reviewing my initial post I think I could have communicated > more clearly. Will everyone please vote on one of the following two options: > > 1. Boost adopts the proposed new logo with Alliance as custodian of the > trademark > > 2. No change I’m not sure I’m a voting member, but I like the new logo. Thanks also for doing all the legal review stuff. -- Adam Getchell https://adamgetchell.org <https://adamgetchell.org/>

2 1

Re: [boost] New Logo Discussion
by Joel de Guzman 18 Jul '24

18 Jul '24

On 7/18/24 9:36 AM, René Ferdinand Rivera Morell wrote: > On Wed, Jul 17, 2024 at 6:50 PM Joel de Guzman via Boost > <boost(a)lists.boost.org> wrote: >> On 7/18/24 3:49 AM, René Ferdinand Rivera Morell via Boost wrote: >>> On Wed, Jul 17, 2024 at 2:42 PM Robert Ramey via Boost >>> <boost(a)lists.boost.org> wrote: >>>> On 7/17/24 11:59 AM, Vinnie Falco via Boost wrote: >>>>> Hi. It is CppCon 2024 season, and the C++ Alliance is working on letting >>>>> people know all the new and exciting things happening in Boost. We're doing >>>>> this with Boost labeled conference shirts, and a beautiful brochure. You >>>>> can see a draft of this promotional piece here (note: work in progress): >>>>> >>>>> https://cppalliance.org/pdf/Boost-Brochure-CppCon-2024.pdf >>>>> >>>> FWIW - I much prefer the current logo which was developed by community >>>> inclusive process with many submissions and designs. >>> It wasn't. The logo picked by the community in that process was never >>> used. What is currently used was the result of private design between >>> the Boost Steering Committee and the artist that "won" that logo >>> contest. >> That is not correct. I was one of the major proponents of that logo contest (if not >> spearheded it). >> And I am not a member of the Boost Steering Committee. That contest was public and was >> discussed in the Boost list. It is NOT a private design. >> >> Here's part of the discussion (I do not have time to search all): >> https://lists.boost.org/Archives/boost//2005/03/81416.php >> >> You can see clearly I was asking for votes. > I did not claim the logo contest was not community driven and resulted > in a community choice. I would know, as I submitted 11 designs in that > context. What I claimed is that the **current** logo was not chosen by > a community process. As the **current** logo was NOT the winning logo. > The winning logo (actually four) was a single, or trio, of stacked > cards (see attached). And as you can see it is very different from > what we have now. I am confused. The winning logo is the beehive design by Zoltan Juhasz https://en.m.wikipedia.org/wiki/File:Boost.png I should know, I tallied the votes. I have no idea what that design you attached is. Regards, -- Joel de Guzman Cycfi Research, Inc.

3 3

Re: [boost] New Logo Discussion
by René Ferdinand Rivera Morell 18 Jul '24

18 Jul '24

On Wed, Jul 17, 2024 at 8:36 PM René Ferdinand Rivera Morell <grafikrobot(a)gmail.com> wrote: > > On Wed, Jul 17, 2024 at 6:50 PM Joel de Guzman via Boost > <boost(a)lists.boost.org> wrote: > > > > On 7/18/24 3:49 AM, René Ferdinand Rivera Morell via Boost wrote: > > > On Wed, Jul 17, 2024 at 2:42 PM Robert Ramey via Boost > > > <boost(a)lists.boost.org> wrote: > > >> On 7/17/24 11:59 AM, Vinnie Falco via Boost wrote: > > >>> Hi. It is CppCon 2024 season, and the C++ Alliance is working on letting > > >>> people know all the new and exciting things happening in Boost. We're doing > > >>> this with Boost labeled conference shirts, and a beautiful brochure. You > > >>> can see a draft of this promotional piece here (note: work in progress): > > >>> > > >>> https://cppalliance.org/pdf/Boost-Brochure-CppCon-2024.pdf > > >>> > > >> FWIW - I much prefer the current logo which was developed by community > > >> inclusive process with many submissions and designs. > > > It wasn't. The logo picked by the community in that process was never > > > used. What is currently used was the result of private design between > > > the Boost Steering Committee and the artist that "won" that logo > > > contest. > > > That is not correct. I was one of the major proponents of that logo contest (if not > > spearheded it). > > And I am not a member of the Boost Steering Committee. That contest was public and was > > discussed in the Boost list. It is NOT a private design. > > > > Here's part of the discussion (I do not have time to search all): > > https://lists.boost.org/Archives/boost//2005/03/81416.php > > > > You can see clearly I was asking for votes. > > I did not claim the logo contest was not community driven and resulted > in a community choice. I would know, as I submitted 11 designs in that > context. What I claimed is that the **current** logo was not chosen by > a community process. As the **current** logo was NOT the winning logo. > The winning logo (actually four) was a single, or trio, of stacked > cards (see attached). And as you can see it is very different from > what we have now. Trying this again because the attachment was too big. :-( See pair of individual images. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

1 0