On Thu, 31 July 2025, 9:47 pm Artyom Beilis via Boost, < boost@lists.boost.org> wrote:
It isn't a question if it is hard or not... Most of the breaking so far was possible to fix this way or other.
Isn't it? You are asking Boost to somehow force maintainers to do something by having a policy of maintaining API stability. I'm just saying I'm good with current (lack of) that policy, and why.
The questions are
- Why do you need to _remove_ the API that hundreds of projects depend on?
It isn't removed (I can still use it). It is still available in the last version that supported that API. - How are users supposed to manage building against different
incompatible versions of Boost?
However they like. Try not to (use multiple) is my go-to answer. The reality is API breaking changes are rare. One way to deal with hard problems is to go around them. I would note modular boost helps re picking and choosing libraries and hence library versions.