July 2024 - Boost-users - lists.stage.boost.cppalliance.org

[release] Boost 1.86.0 beta 1 released
by Marshall Clow 26 Jul '24

26 Jul '24

Boost release 1.86.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.86.0.beta1/source/ The SHA256 checksums are: 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1.zip cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1.7z 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1.tar.gz Release notes (still need updates): https://www.boost.org/users/history/version_1_86_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. Thanks especially to Sam Darwin for his help with the tools, and figuring out what happend with RC3. -- Boost Release Team

1 0

error: template argument for template type parameter must be a type template< class Allocator = std::allocator< none > >
by Phil Phil 05 Jul '24

05 Jul '24

Greetings, I try to port a c++ project to a new environment with clang++-17, libcxx 17 and std=c++17 for x64 Linux. Also, I switched form boost 1.65 to 1.84. Now I start getting errors in boost itself: /workspace/usr/include/boost/statechart/fifo_worker.hpp:55:45: error: template argument for template type parameter must be a type 55 | template< class Allocator = std::allocator< none > > As far as I know this has to do with deprecation of some variable type in allocator. Any ideas how I might fix this on short notice? Regards

2 2

directory_iterator UNC path
by Lars Sunde 04 Jul '24

04 Jul '24

Hello, Using boost::filesystem::directory_iterator with an UNC path failed with Boost 1.84 and Windows 10. Did some research on this topic and found this bug report from 2022; https://github.com/boostorg/filesystem/issues/245 This issue contain a link to this fix; https://github.com/boostorg/filesystem/commit/9c9d127bddc2b72187c57f4933c49… When looking at boost 1.84 and 1.85 source code I cannot find the fix shown above. Please excuse my ignorance but what is the relationship between https://github.com/boostorg/filesystem and the sw released at https://www.boost.org<https://www.boost.org/> ? Kind regards, Lars [https://opengraph.githubassets.com/d5334b4df3942668241ead9dde0a136ddc1b0979…]<https://github.com/boostorg/filesystem> GitHub - boostorg/filesystem: Boost.org filesystem module<https://github.com/boostorg/filesystem> Boost.org filesystem module. Contribute to boostorg/filesystem development by creating an account on GitHub. github.com

2 2