El 20/10/2026 a las 18:25, Joaquin M López Muñoz via Boost escribió:
It is generally known within the community that some of the libraries in Boost are not being properly maintained: issues pile up without a prompt (or any) response from the nominal maintainers, eroding the libraries' usefulness and, ultimately, their viability. There are a number of stalwart contributors (Peter Dimov, Andrey Semashev, and others) who work to make sure CI tests stay green throughout the project, but beyond that they can't possibly address outstanding issues and evolution requests for all libraries.
Thanks Joaquín for starting this thread and also to all those heroes maintaining the hard stuff of many unmaintained libraries.
Any initiative to try to remedy this situation begins with identifying its true extent. My colleagues at the FSC and I have gone through all Boost libraries and identified those that we regard as unmaintained, as evidenced by the presence of many important issues that go unresolved without anyone addressing them. This is the list:
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
Although op-topic, one little contribution I can propose is to take the maintenance of circular_buffer, which is a container that is not in the standard. One option is to refactor it inside Boost.Container and put it in the same level/features as other containers. Since Boost.Container also has some allocators, I could also take care of pool.
Any such assessment is a little fuzzy by definition, so the cutoff point for what's considered maintained or not is subject to discussion. I'd like to request your feedback:
* If you think some entry in this list should be removed (because you're the maintainer or you know the library is actually maintained and we got it wrong), please say so. * Conversely, tell us if you feel some Boost library not in the list should be included.
* Please share any ideas on how to improve the situation so that we get more people actively maintaining more libraries. For starters, unmaintained libraries could be labeled as such on the website to attract people potentially interested in taking over (and to warn potential users about long-term adoption risks).
That seems a good idea. Several libraries are domain-specific (odeint, accumulators, compute....) so we'd really need people with specific knowledge to have a high quality maintenance. Note that some of those libraries seem to have very few reverse dependencies. This means that we could drop them without causing problems in other Boost libraries. Library / Direct reverse deps / Transitive reverse deps ------------------------------------------------------- accumulators / 0 / 0 contract / 0 / 0 convert / 0 / 0 hof / 0 / 0 local_function / 0 / 0 odeint / 0 / 0 statechart / 0 / 0 stl_interfaces / 0 / 0 yap / 0 / 0 Others could be deprecated / erased working on a single reverse direct dependency: tti / 1 / graph functional / 1 / multi_array vmd / 1 / type_erasure callable_traits / 1 / cobalt multi_array / 1 / numeric~odeint polygon / 1 / geometry ptr_container / 1 / assign scope_exit / 1 / local_function type_erasure / 1 / poly_collection units / 1 / numeric~odeint Best, Ion ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ ------------------------------------------------------ PD: Attached the list of the identified libraries, ordered by direct reverse dependency count (Boost 1.92). ----------------------------------------------------- Library / Direct reverse deps / Direct dependents accumulators / 0 / - contract / 0 / - convert / 0 / - hof / 0 / - local_function / 0 / - odeint / 0 / - statechart / 0 / - stl_interfaces / 0 / - yap / 0 / - callable_traits / 1 / cobalt multi_array / 1 / numeric~odeint polygon / 1 / geometry ptr_container / 1 / assign scope_exit / 1 / local_function type_erasure / 1 / poly_collection units / 1 / numeric~odeint functional / 1 / multi_array vmd / 1 / type_erasure tti / 1 / graph format / 2 / fiber, wave hana / 2 / parser, yap rational / 2 / geometry, icl ublas / 2 / accumulators, numeric~odeint compute / 2 / numeric~odeint, numeric~ublas xpressive / 2 / graph, log lambda / 2 / bimap, units logic / 3 / beast, numeric~interval, safe_numerics property_tree / 3 / compute, graph, log phoenix / 3 / log, msm, spirit pool / 3 / context, spirit, wave circular_buffer / 4 / accumulators, cobalt, msm, ptr_container foreach / 4 / graph, graph_parallel, mpi, python date_time / 4 / asio, icl, log, thread tokenizer / 4 / date_time, geometry, process, program_options variant / 5 / geometry, graph_parallel, serialization, signals2, spirit proto / 6 / compute, log, msm, phoenix, spirit, xpressive align / 6 / asio, atomic, lockfree, log, python, url numeric_conversion / 8 / accumulators, date_time, geometry, graph, iostreams, python, test, xpressive function_types / 9 / compute, contract, convert, functional, fusion, geometry, log, spirit, tti parameter / 10 / accumulators, convert, flyweight, graph, heap, lockfree, log, msm, parameter_python, signals2 fusion / 15 / accumulators, compute, geometry, hana, iterator, log, msm, numeric~odeint, parameter, phoenix, process, proto, spirit, type_erasure, xpressive tuple / 16 / accumulators, algorithm, assign, compute, exception, fusion, geometry, graph, graph_parallel, hana, lambda, multi_index, python, range, signals2, thread integer / 18 / chrono, gil, graph, iostreams, math, mpi, multi_index, multiprecision, pool, python, random, rational, safe_numerics, serialization, spirit, units, variant, xpressive concept_check / 21 / accumulators, algorithm, bimap, circular_buffer, geometry, gil, graph, graph_parallel, heap, icl, iterator, math, multi_array, numeric~ublas, property_map, property_map_parallel, range, regex, safe_numerics, thread, wave range / 22 / accumulators, algorithm, assign, compute, convert, date_time, foreach, geometry, graph, icl, iostreams, log, mqtt5, numeric~odeint, numeric~ublas, phoenix, property_tree, proto, ptr_container, sort, spirit, xpressive preprocessor / 47 / accumulators, assign, atomic, bimap, cobalt, compute, concept_check, contract, detail, flyweight, function_types, functional, fusion, gil, graph, iostreams, lambda, local_function, log, metaparse, mpl, msm, multi_index, numeric~conversion, numeric~odeint, openmethod, parameter, parameter_python, phoenix, proto, python, range, scope_exit, serialization, signals2, spirit, test, thread, tti, type_erasure, units, utility, variant, vmd, wave, xpressive, yap