El 21/10/2026 a las 23:43, Ion Gaztañaga escribió:
El 20/10/2026 a las 18:25, Joaquin M López Muñoz via Boost escribió:
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.
That'd be much appreciated! As for merging circular_buffer into container or not, I have no strong opinion either way. We've learnt how to do it with static_assert, in any case. Joaquín M López Muñoz