July 2023 - Boost - lists.stage.boost.cppalliance.org

CMake Announcement from Boost Steering Committee
by Jon Kalb 13 Aug '24

13 Aug '24

The libraries produced by the Boost community have had a greater impact on the way that the C++ community writes code than any other library implementation. The focus of the Boost community will always be on the libraries, but it is undeniable that we are dependent on and often limited by the infrastructure of our trade. Years ago, the move to Git was contentious; yet, it was required to improve development. In a similar vein our build system has become an impediment for many developers and users, existing and prospective. Therefore, we, the Steering Committee, announce to the Boost community our desire and intent to move Boost’s build system to CMake for users and developers alike. We are soliciting comments and proposals from the community to guide the process and the goals. Our desire is that the community can come to consensus by the end of the calendar year with a vision of supporting users and developers. We understand that the actual process of achieving the end goal will be long, time consuming, and not without its share of conflict. We also recognize that the Boost community is comprised of bright and passionate individuals that are eager to get involved and help get work done. The members of the Steering Committee have been encouraged by the discussions and activity surrounding CMake on the mailing lists over the years and know that many people have voiced visions. We hope that each of you rejoins the discussion to support this initiative and contributes to the common goal of improving Boost’s integration into the broader C++ ecosystem. For the Boost Steering Committee, Jon Kalb, Chair jonkalb(a)boost.org

49 199

Boost Governance?
by René Ferdinand Rivera Morell 09 Aug '24

09 Aug '24

A disclaimer: I write this solely as a Boost Library author. And not in any other capacity or representing any other interest. It's now been at least a year since Boost switched from the Software Freedom Conservancy to the Boost Foundation for its governance organization. But have people noticed any difference? Did you know that switch happened? Did you know that they held an election for the Board of Directors and for the Officers? Do you know when that election happened? Do you know who got elected? Do you know how they were selected? Do you know what their responsibilities are? Do you know what their bylaws are? Do you know their financials? More importantly: Did you answer "no" to any of those questions? As a library author, I can say I definitely answered no to many of those questions. This is a problem. As authors, without asking, we should know those answers from the organization that governs our work. We should have input into how that organization governs. In other words, we deserve open and transparent governance; not the closed and opaque status quo. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

10 9

Paul Bristow
by John Maddock 08 Aug '24

08 Aug '24

I've just heard that Paul Bristow who helped so much with the development of Boost.Math and indeed many other libraries, passed away peacefully last week. RIP Paul. Much missed. John.

6 5

Library proposal - indexed_array
by Julien Blanc 12 Oct '23

12 Oct '23

Hi, I've written and released a (rather small) library which allows defining arrays with arbitrary index mechanisms (hence the name, indexed_array). This especially allows indexing with scoped enums, use non zero-starting indexes, or use sparse indexes. This is not a view, but an array in the sense that it owns the data, and provides the same guarantees and functionalities as std::array, such as triviality propagation, being able to reside in read-only program sections, etc. It also supports multidimensional indexing, and provides an indexed_span template class to access lower dimension content (which can be used outside indexed_array). Finally, it provides an opt-in safer way to initialize the array content, which is especially useful when using complex and/or changing indexing schemes (like based on externally generated files). The library is available here: https://github.com/Julien-Blanc-tgcm/indexed_array And the doc is here: https://julien-blanc-tgcm.github.io/indexed_array/ It requires C++17 and mp11, and has first-class support for describe-d enums. If there is some interest, i'd like to propose it for inclusion in boost. So i'm looking for people who would endorse it. Thanks and best regards, Julien

8 24

Master Branch is now open for bug fixes
by Marshall Clow 02 Aug '23

02 Aug '23

The master branch is now open for bug fixes and documentation changes. Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy The next deadline: On August 5th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — Marshall

4 7

oneAPI build
by Alain O' Miniussi 01 Aug '23

01 Aug '23

Hi, I'm trying to build master with oneAPI 2023.1.0's icpx. So far I am mostly getting warnings for unknown/unsupported options like: icpx: warning: -Wl,-rpath,/data/spack/opt/spack/linux-centos7-x86_64/gcc-12.2.0/intel-oneapi-mkl-2023.1.0-x6dxpakvvn4sntkmbzqvtjdndc3g5ttn/mkl/2023.1.0/lib/intel64: 'linker' input unused [-Wunused-command-line-argument] intel-linux.compile.c++ bin.v2/libs/log/build/intel-linux-2023.1.0/release/cxxstd-17-iso/threading-multi/visibility-hidden/setup/matches_relation_factory.o icpx: command line warning #10430: Unsupported command line options encountered These options as listed are not supported. For more information, use '-qnextgen-diag'. option list: -ip -wd177,780,2196,1782,193,304,981,1418,411,734,279 Is oneAPI supported ? the following page: https://www.intel.com/content/www/us/en/developer/articles/technical/buildi… only mention 1.75 and 1.78 Thanks Alain

2 2

Request to merge fixes to docca
by Krystian Stasiowski 28 Jul '23

28 Jul '23

I would like to merge the following commits: https://github.com/boostorg/docca/commit/0ce4e198398dbb52f1de0029f4ed9b7d2b… https://github.com/boostorg/docca/commit/8ba36c0c1e1adb32dbf4cd9c7f3cb36f33… https://github.com/boostorg/docca/commit/4b61682742d6fc0d373698d42635024088… To address these issues: https://github.com/boostorg/docca/issues/136 https://github.com/boostorg/docca/issues/105 These fix assorted compatibility issues with doxygen 1.8.16 and newer

2 1

[boost.async] Seeking Endorsement
by Klemens Morgenstern 28 Jul '23

28 Jul '23

Dear fellow Boost developers, I am seeking endorsement for my C++20 async coroutine library boost.async. It provides coroutine primitives & utilities that are easy to use and intuitive, to anyone who has seen python's asyncio or javascripts async/await APIs before. It simplifies using asio and increases compile times significantly by encouraging the usage of translations units. The features include: - coroutine types (eager, lazy, generators) - built-in cancellation - synchronization of multiple coroutines (select, gather, join) - channels - with (an async scope akin to python's with expression) - asio integration, i.e. completion tokens I think this kind of library is much needed in boost and the wider C++ community. code: https://github.com/klemens-morgenstern/async docs: https://klemens.dev/async/

11 31

Request to merge a fix to Boost.Core
by Peter Dimov 26 Jul '23

26 Jul '23

May I please merge the following fix https://github.com/boostorg/core/commit/c7134904e27237dbbb81ba28f0f23fc365b… to address issue https://github.com/boostorg/core/issues/150 ? I can't verify that the fix actually works, but it doesn't affect non-Android platforms, so can't make things any worse.

2 1

Re: [boost] Request to merge bug fixes in Boost.Outcome
by Niall Douglas 25 Jul '23

25 Jul '23

On 20/07/2023 11:36, Niall Douglas wrote: > Can I get permission to merge a few small bug fixes plus docs fixes? > > https://github.com/boostorg/outcome/commits/develop > > 1. Changes just before the beta window breaks build on C++ 14 in certain > corner cases, fixed. > > 2. Experimental Outcome Boost result did not compile due to changes to > status code by LEWG, fixed. > > 3. Docs fixes also due to the LEWG renaming breaking docs examples. > > 4. Failure to compile Experimental Outcome on FreeBSD fixed. Ping on the above. Niall

2 2