El 20/10/2026 a las 22:17, Kai Bartels via Boost escribió:
On 20/10/2026 18:44, Matt Borland via Boost wrote:
accumulators, align, callable_traits, circular_buffer, compute, concept_check, contract, convert, date_time, foreach, format, function_types, functional, fusion, hana, hof, integer, lambda, local_function, logic, multi_array, numeric_conversion, odeint, parameter, phoenix, polygon, pool, preprocessor, property_tree, proto, ptr_container, range, rational, scope_exit, statechart, stl_interfaces, tokenizer, tti, tuple, type_erasure, ublas, units, variant, vmd, xpressive, yap
Should we think about retiring and removing libraries for some of these? For example: foreach and tuple should have been replaced C++11 and scope replaces scope_exit. My first reaction was: sure, yes! Example tuple: users can just use std::tuple, if they have C++11+, or continue using the current version of boost tuple. The current version is like the previous version, is like the next version, when unmaintained.
But the thoughts and information highlighted by Arnaud, Peter and Peter, later in this thread, seem to show that this might be quite laborious in the end; the crux being the internal dependencies and minimal C++ version targeted by some (other) libraries. Continuing the tuple example: tuple is used by multi_index (P.D.) multi_index is classified active,maintained,unique (P.T.) multi_index aims for C++03 (P.T.) => multi_index can't switch to std::tuple . (Just the first example I found.)
Re MultiIndex, the library actually requires C++11 (https://github.com/boostorg/multi_index/blob/develop/meta/libraries.json). Starting with Boost 1.91, most user-facing tuples are std::tuples or either both boost::tuple and std::tuple are equally accepted (https://www.boost.org/doc/libs/latest/libs/multi_index/doc/release_notes.htm...). The remanining hard dependency on Boost.Tuple is in multi_index_container::ctor_args_list, but this could be eliminated without much effort should Boost.Tuple cease to exist. Joaquín M López Muñoz