5 May
2022
5 May
'22
2:58 p.m.
On Thu, 5 May 2022 at 16:26, Kostas Savvidis via Boost
[...] In other words, boost needs to shrink not grow.
I mostly agree, but I'd say Boost needs to undergo a restructurisation to remain attractive to all generations of developers, maintainers and users. I can't see it happen unless we have separate superprojects: github.com/boostorg/boost (require>=C++17) github.com/boostorg/boost11 (>=C++11 ) and, if still relevant, perhaps: github.com/boostorg/boost03 As a maintainer, I'd like to be free to maintain a library only for e.g. boostorg/boost and forget about boostorg/boost11, or let new maintainer to take it over there. Best regards -- Mateusz Loskot, http://mateusz.loskot.net