July 2023 - Boost - lists.preview.boost.org

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

Bug fixes in Boost.URL
by Alan de Freitas 21 Jul '23

21 Jul '23

I would like to ask for permission to merge the following bug fixes to master in Boost.URL: - c97bc278: parse_query does not recreate string_view - 0ca58467: url_view string_view constructor requires non-url_view_base - f2bb191b: IP-literal can be IPv6addrz Thanks -- Alan Freitas https://alandefreitas.github.io/alandefreitas/ <https://github.com/alandefreitas>

2 1

Request to merge bug fixes in Boost.Outcome
by Niall Douglas 20 Jul '23

20 Jul '23

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. Niall

2 1

boost::normal_distribution<>(boost::mt19937) changed behavior from 1.60 to 1.80
by Foelsche, Peter 18 Jul '23

18 Jul '23

Dear All, I'm not certain if the behavior I'm seeing is expected or a problem. I'm getting different series of numbers from the two different boost versions in question. When running a diff on the output I'm getting numbers inserted in one series or the other and then the two series become identical again. Below is the source. I'm using the following series of commands: g++ -std=c++14 test.cpp -g -DNDEBUG -fwhole-program -I/mnt/share/boost/boost-1.80/include -o 180 g++ -std=c++14 test.cpp -g -DNDEBUG -fwhole-program -o 160 ./180 16384 2078781393 1 > 180.txt ./160 16384 2078781393 1 > 160.txt diff 160.txt 180.txt |more The first difference is at line 284. The next at 364, 1783, 2685. Peter PS. g++ (GCC) 5.3.0 PPS. The source #include <boost/random.hpp> #include <boost/version.hpp> //#include <boost/random/variate_generator.hpp> #include <boost/random/mersenne_twister.hpp> #include <boost/random/normal_distribution.hpp> #include <boost/random/uniform_int_distribution.hpp> #include <limits> #include <iostream> int main(int, char**argv) { std::cout << BOOST_LIB_VERSION << std::endl; const auto bOld = std::atoi(argv[3]) != 0; boost::mt19937 sGenerator; sGenerator.seed(std::atoi(argv[2])); //boost::random::uniform_int_distribution<> sDist(0, std::numeric_limits<int>::max()); boost::normal_distribution<> sDist(0.0, 1.0); boost::variate_generator<boost::mt19937, boost::normal_distribution<> > sGen(sGenerator, sDist); for (int i = 0, iMax = std::atoi(argv[1]); i < iMax; ++i) if (bOld) std::cout << sDist(sGenerator) << std::endl; else std::cout << sGen() << std::endl; }

2 1