- Boost - lists.boost.org

Why no "w != NULL" assertion before boost/intrusive/rbtree_algorithms.hpp:511 like before the line 476?
by achinkoff＠gmail.com 13 Aug '25

13 Aug '25

Boost version: latest release file: boost/intrusive/rbtree_algorithms.hpp function: rebalance_after_erasure_restore_invariants in this if-branch ``` if(x == x_parent_left){ //x is left child ``` there is "w != NULL" assertion before variable 'w' access: ``` BOOST_INTRUSIVE_INVARIANT_ASSERT(w); if(NodeTraits::get_color(w) == NodeTraits::red()){ ``` but in else-branch there is no same assertion before variable 'w' access: ``` if(NodeTraits::get_color(w) == NodeTraits::red()){ ``` Why? Are there no assertion in else-branch intentionally due to the rbtree structure itself? Thanks.

2 1

A proposal for a modern build-system
by Hassan Sajjad 08 Aug '25

08 Aug '25

Hi. I compiled 25 Boost libraries with C++20 header-units, including examples and Tests of a few. This resulted in a 1.44x speed-up if we exclude the scanning. Scanning was as slow as the header-unit build. I have a solution for that. I am sending this paper (Making some final edits) https://htmlpreview.github.io/?https://github.com/HassanSajjad-302/iso-pape… , which allows for a build-system to use a scanning-less approach to build header-units.This method requires only minimal modifications to the compiler and enables memory-mapped file sharing, which significantly reduces filesystem overhead and further boosts speed. My proposal for a scanning-less approach will allow HMake to have another amazing feature, monolithic Big header-units. BigHu will allow you to map all the headers from a directory to a single header-unit. This header-unit includes all these header-files and consumes them as header-files. Now, whenever the compiler requests a header-unit from this directory, the build-system instead sends this consolidated BigHu. This will not only improve the clean build speed, because of fewer process launches. But also massively boosts the rebuild speed as few header-units need to be read instead of lots of files. No source-code editing will be needed to use this feature. And you will have the option to either build a library as BigHu (if you don't mean to edit it) or as small header-units (if you are working on it). HMake will soon support compile_commands.json, which I guess can work fine with header-units. Thus you can benefit from both, faster compilation and working intelliscence. The API shown in hmake.cpp is a work in progress. HMake build-system benefits are numerous, even if we leave out the header-units support. This makes it a perfect replacement for B2. I believe we can complete the switch in the next 2 months. And if some compiler supports my paper, we get >3x faster compilation as well. Best, Hassan Sajjad

25 78

[release] Master branch is now closed for the release
by Marshall Clow 07 Aug '25

07 Aug '25

Master is closed for all changes. See the release schedule at http://www.boost.org/calendar — The release managers

1 0

C++26 Reflection in Boost
by Vinnie Falco 07 Aug '25

07 Aug '25

Which Boost libraries would benefit from implementing C++26 reflection? For my libraries that includes: Boost.JSON what other libraries?

8 9

[release] The Master branch will be closing for the 1.89.0 release on Wednesday, 6-August
by Marshall Clow 06 Aug '25

06 Aug '25

Calendar is here: https://www.boost.org/calendar Current status of the master branch: Master is open for bug fixes and documentation updates. Other changes by permission of a release manager. — The release managers

3 2

New and Improved Decimal Library
by Matt Borland 02 Aug '25

02 Aug '25

It has been about 6 months since the indeterminate end of the Decimal review, but Chris and I wanted to announce the newest major version of the library (v5.0.0). What has changed? Quite a lot: Breaking Changes: - Based on bitwise comparisons with other similar libraries and database software, we have changed the internal encoding of our IEEE 754-compliant types - We spent about 3 months optimizing just back end integer types that are now used throughout the library and as the internals of decimal128_t - We have changed the type names to better match conventions: - decimalXX is now decimalXX_t - decimalXX_fast is now decimal_fastXX_t - The headers have been similarly renamed, and can now be used independently instead of requiring the monolith based on feedback in Review - Constructors have been simplified to reduce confusion Other Changes: - The doc content have been overhauled thanks to feedback from Peter Turcan and others during the review - The docs are no longer a single long page of Asciidoc; we have moved to Antora. Thanks to Joaquín and Christian for making it trivial to copy from Unordered to make that happen. - https://develop.decimal.cpp.al/ - We now support formatting with {fmt} - Benchmarks have been expanded to include GCC _Decimal types, and Intel's libbid. I think people should be pleased with the results now, since that was a huge point of contention at the end of the review - Every post-review issue John was kind enough to consolidate and open have been addressed Thanks to all those that helped make the library better than it was. Let us know if you find any new issues, or need a feature, as you try the new version. Chris and I are thinking about doing the re-review in the Fall; stay tuned. Matt

3 4

[release] Master branch is now open for bug fixes
by Marshall Clow 28 Jul '25

28 Jul '25

Hi, The master branch is now open for bug fixes, test and documentation changes, but please follow the policy described in: https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy The next deadline: On August 6th, master closes for all changes. As always, the calendar is at https://www.boost.org/calendar — The release managers

7 10

Boost 1.89.0.beta1 Asio potential bug
by Ruben Perez 27 Jul '25

27 Jul '25

I'd like to call attention on this problem I had with Asio, which I think is a legitimate bug: https://github.com/chriskohlhoff/asio/issues/1650 It's currently making Boost.MySQL CIs fail. It'd be good if it could be fixed for the release. Thanks, Ruben.

1 0

[release] Boost 1.89.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 23 Jul '25

23 Jul '25

Available at: https://archives.boost.io/beta/1.89.0.beta1/source/ The SHA256 checksums are as follows: bf45af4a58f39c2ec374ef6e70b26859b786ba2ed087bc869d92a2b4de14e0d2 boost_1_89_0_b1_rc1.zip f255b4a31558b3fb81be1dc7e8b367fb9997dbe5e71da98a730c681377abffa9 boost_1_89_0_b1_rc1.7z 984ee193ddf192795ba635d4c73b2b43e1e596995d7ce5519a3a72fab9bc0b40 boost_1_89_0_b1_rc1.tar.gz 9ece9af2b243f90b76f679b278b512b6589c7843e4dd54cffcb719bbc0801998 boost_1_89_0_b1_rc1.tar.bz2 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 11

Asio: can a asyn_write handler came after a asyn_read handler?
by Dennis Luehring 22 Jul '25

22 Jul '25

Asio 1.88 im currently trying to understand a TCP server/client implementation at a new customer project the statemachine of the user code bases on the fact that a handler of an async_write needs to always comes before the handler of an async_read i don't think that is guaranteed, is it? this is the redcuded scenario: an async_read wait for a single reply from the connected sever a single async_write is done that make the server reply a single paket in the waiting aysnc_read is it possible that the async_write handler comes after the async_read handler? i had a look at the Asio implementation for Windows and it seems that the write handler will be come before - but im not that deep in the implementation

3 5