В письме от вторник, 20 октября 2026 г. 21:25:45 MSK пользователь Arnaud Becheler via Boost написал:
Unless a library is entirely non-functional, I don't see how removing it would help anyone.
I think different people are optimizing along different axes:
1. Maintenance allocation... 2. Discoverability... 3. Cross repository cost...
What if we created a project for legacy libraries? I mean specifically unmaintained libraries that don't have Boost users and shouldn't have new users. E.g. StaticAssert was moved to Config, but the project is still there. Foreach probably can be trivially replaced everywhere in Boost with for loops, since we effectively require C++11 for almost all libraries. So, let's create a Legacy library that will be the place of final rest with these obsolete libraries. That would significantly simplify required maintenance for them. It would be one build.jam, one CMakeLists.txt, one meta/libraries.json, include directory, possibly example and/or test directories, no or very bare bones CI (just check that headers are installed). Maintaining such project would pretty much involve only updating build scripts when something in the superproject changes or when another library becomes legacy. I personally can volunteer to do that. Of course, the simplicity of this arrangement relies on these libraries being header-only. E.g., it wouldn't be applicable to Coroutine.