On 9/12/25 7:11 AM, Andrey Semashev via Boost wrote:
On 12 Sep 2025 01:06, Nana Sakisaka via Boost wrote:
2025年9月12日(金) 4:17 Joel de Guzman via Boost <boost@lists.boost.org>:
Due to some backlash with this PR, mostly due to breaking changes. We should probably ease up and rethink what we are doing here. Boost thrives on consensus, and the discussions seem to be going in a negative direction, which should be addressed both in the PR and in this mailing list.
I urge the parties to raise the issues the the PR:
https://github.com/boostorg/spirit/pull/807
FWIW, my position is that I am all for modernizing and moving to C++23, but it should be done carefully and with consideration to users of Spirit X3 and Boost in general. Re-quoting this message to inform the list that further discussions should take place on the specific link Joel mentioned. Personally, it looks like there's confusion as to which Spirit version serves which purpose, and in particular, which version should be considered production-ready by users. I think, the decision needs to be made by the Spirit maintainers and then announced here and in release notes. I do not think the PR comments are the appropriate place to discuss this decision (if such as discussion should happen) because (a) this goes beyond the X3 refactoring work done in the PR and (b) the PR comments are not as discoverable as this ML and release notes.
Agreed. For any major update, I suggest starting a discussion in Github's discussion pages and informing the list about it. That being said, I urge the Boost community to maintain a kind and welcoming tone. That was not the case in the message that started this thread. Maintaining a library is NOT a trivial task, everyone knows that, and it is disheartening to see maintainers leave because of the toxicity. Here's one from @Kolejey from May 8: "The main reason I've stopped working on improvements is because I got yelled pretty much every time I fix a bug or change some internal stuff that no one should've relied on. And I get their viewpoint, Boost nowadays is seen as a collection of mostly legacy battle- tested libraries, a project uses Boost because it have used it for a long while and people that maintain it don't want their working code been disturbed." And this reflects the scenario we have now, again. Regards, -- Joel de Guzman Cycfi Research, Inc.