- Boost - lists.boost.org

Issue fixed in context library that is not included in 1.88 beta release?
by Anders Axelsson 29 Mar '25

29 Mar '25

Hi, I stumbled upon a problem found in the 1.87.0 release (and also 1.88 beta1) The issue seems to have been resolved on the develop branch in the actual submodule repo quite some time ago by another developer, but it is yet not included in the top/super project. The ticket: https://github.com/boostorg/context/issues/297 I am very new to the community, so I don't really know what is the typical way of working here. it would be sad if we miss to include an important build issue in the next release just because of some administrative issues, so I am happy to help but like I said, I am not familiar with how I can do that. Any ideas?

3 3

Asio Beta changes are missing on the 1.88 Beta page
by Dennis Luehring 27 Mar '25

27 Mar '25

Asio is missing on the beta release page https://www.boost.org/users/history/version_1_88_0.html but there seem to be changes available for the beta https://www.boost.org/doc/libs/1_88_0_beta1/doc/html/boost_asio/history.html

1 0

Reminder: Master branch closes for the 1.88.0 release NEXT WEDNESDAY
by Marshall Clow 26 Mar '25

26 Mar '25

Also, if you have release notes, now’s the time to write them. — Marshall

1 0

release] Boost 1.88.0 beta 1 released
by Marshall Clow 16 Mar '25

16 Mar '25

Boost release 1.88.0 beta 1 is now available at: https://archives.boost.io/beta/1.88.0.beta1/source/ The SHA256 checksums are: bc4948bc664fde0c2142badae2679a42124b464dc58019250afe0ef57fd7763e boost_1_88_0_rc1.zip 3c334a9a743b68a35452b0223be8932fb39f26a6938382f9b9e625c4df99602c boost_1_88_0_rc1.tar.gz 9e42c0611500151d795d66a07ef0a21036c02d24678e2e887caf6d97fcbc25ca boost_1_88_0_rc1.tar.bz2 7faf60c4cb12ee90270e41716cf3735a8739016d7346983ce9f5e899e510b26d boost_1_88_0_rc1.7z Release notes (still need updates): https://www.boost.org/users/history/version_1_88_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

3 2

[release] Boost 1.88.0 Release Candidate 1 is available
by Marshall Clow 14 Mar '25

14 Mar '25

Available at: https://archives.boost.io/beta/1.88.0.beta1/source/ The SHA256 checksums are as follows: bc4948bc664fde0c2142badae2679a42124b464dc58019250afe0ef57fd7763e boost_1_88_0_b1_rc1.zip 3c334a9a743b68a35452b0223be8932fb39f26a6938382f9b9e625c4df99602c boost_1_88_0_b1_rc1.tar.gz 9e42c0611500151d795d66a07ef0a21036c02d24678e2e887caf6d97fcbc25ca boost_1_88_0_b1_rc1.tar.bz2 7faf60c4cb12ee90270e41716cf3735a8739016d7346983ce9f5e899e510b26d boost_1_88_0_b1_rc1.7z 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 10

[proposal] OpenMethod library
by Jean-Louis Leroy 11 Mar '25

11 Mar '25

Hello Boost developers! I would like to propose my open-method library for inclusion in Boost. Open-methods are an elegant solution to the Expression Problem: > Given a set of types, and a set of operations on these types, is it possible > to add new operations on the existing types, and new types to the existing > operations, without modifying existing code? Open-methods solve the Expression Problem by making it possible to define free virtual functions, i.e. virtual functions that exist outside of a class. They also help reduce coupling. Open-methods are often called "multi-methods", because they typically make it possible to select an overrider on the basis of more than one argument (as this library does). Nice, but this is a distraction. Observations show that single dispatch largely outnumbers multiple dispatch in real systems, even in languages that natively support multi-methods (Common Lisp, Clojure, Julia, Dylan, TADS, Cecil, Diesel, Nice, etc). "Multi" is just the cherry on the "open" cake. Bjarne Stroustrup wanted open-methods in C++ almost from the beginning. In D&E he writes: > I repeatedly considered a mechanism for a virtual function call based on more > than one object, often called multi-methods. [...] Since about 1985, I have > always felt some twinge of regret for not providing multi-methods. > Stroustrup, 1994, The Design and Evolution of C++, 13.8. Circa 2007, he tried to bring open-methods into the standard, unfortunately without success, to his enduring regret. Decades later he writes: > In retrospect, I don’t think that the object-oriented notation (e.g., x.f(y)) > should ever have been introduced. The traditional mathematical notation f(x,y) > is sufficient. As a side benefit, the mathematical notation would naturally > have given us multi-methods, thereby saving us from the visitor pattern > workaround. > Stroustrup, 2020, Thriving in a Crowded and Changing World: C++ 2006–2020. This is what this library is all about: f(x, y), and getting rid of visitors. It closely follows the design described in the papers by Stroustrup and his PhD students Peter Pirkelbauer and Yuriy Solodkyy. Method dispatch is *fast*. It uses v-tables similar to native virtual functions, and it can match their performance. The library also provides additional features: a mechanism to call the next most specialized overrider, support for smart pointers, customization points for alternative RTTI systems, error handling, tracing, etc. The library requires C++17 or above. It supports virtual and multiple inheritance, excluding repeated inheritance. For evaluation purposes, I prepared a repository with a library adapted to Boost naming conventions: https://github.com/jll63/Boost.OpenMethod. The documentation is here: https://jll63.github.io/Boost.OpenMethod. Here are a few examples from the tutorial on Compiler Explorer: * Hello World: https://godbolt.org/z/9hv8oE8zd * AST - combining virtual_ptr and std::unique_ptr: https://godbolt.org/z/cPjzfanc8 * Intrusive vptr: https://godbolt.org/z/87h9zv7dK * Policy for throwing exceptions: https://godbolt.org/z/nEYWGsPc5 If you like what you see, please consider endorsing the library. Thanks, Jean-Louis Leroy

6 11

[Release] Master branch is now closed for the beta release
by Marshall Clow 09 Mar '25

09 Mar '25

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

1 0

[release] Master branch closes for the 1.88.0 beta release on SATURDAY (March 8)
by Ion Gaztañaga 06 Mar '25

06 Mar '25

Hi, Due to some unexpected delays, the master branch will close on SATURDAY (March 8). — The Release Managers

1 0

MAP and Vector clear is not releasing memory
by Murali Kishore 26 Feb '25

26 Feb '25

Hi, map and vector stored in shared memory using boost apis and called clear to release memory. when i insert same key i see old data present. want to check using boost map.clear or vec.clear is not removing content. Example: pod_list[] (vector contains following 3 members) pod_info { pod_id du_map. cell_map. } Step 1: Added elements Step 2: pod_list.clear(); Step 3: observed no elements in pod_list empty Step 4: Added only key pod_info.pod_id = 1; pod_list.insert(pod_info); Step 5: i see old content map to this pod_id. after this expecting du_map.size and cell_map size is empty. but du_map,cell_map content is same as before clear want to check is clear will not remove memory? is any other best way to clean this vector. -- Regards, Murali Kishore

2 2

Master branch now closed for new libraries and breaking changes
by Marshall Clow 26 Feb '25

26 Feb '25

Welcome to the start of the 1.88.0 release cycle. The release branch is now closed for new libraries and breaking changes to existing libraries. Still open for bug fixes and other routine changes to all libraries without release manager review. The next deadline is next Wednesday, when the release branch will be closed for major changes. As always, the calendar is here: https://www.boost.org/development/index.html — The release managers

2 1