2025年9月12日(金) 9:35 Joel de Guzman via Boost <boost@lists.boost.org>:
On 9/12/25 7:13 AM, Peter Dimov via Boost wrote:
I think that we should give serious consideration to the idea of rolling back X3 to its previous C++17 state and instead making a separate "version 4" Spirit that is C++23 and where new development can be focused.
As Alexander points out in the issue, this will also make the boostorg/spirit split unnecessary (although we can still go ahead with it if we decide it's a good idea for other reasons.)
This way people who can't move past C++17 for various reasons (such as the MQTT5 users) can still continue using X3.
I concur. This is the right way to go. Nana Sakisaka, is that a direction you'd be interested to pursue? This is the safest path forward.
As a Spirit maintainer, I've decided it is time to start Spirit.X4. I believe the name "Spirit.X4" is the right choice because it reflects the spirit of Spirit, as Joel mentioned here: https://github.com/boostorg/spirit/pull/807#issuecomment-3282965760 After the migration is complete, I plan to return the existing `boostorg/spirit` codebase to a C++17 baseline, as Peter suggested. ---------------------------------------------------------- Request to core members: - Please create a new repository, `boostorg/spirit_x4`, and grant permissions to my account, @saki7. - I'm requesting full (admin) access for the new repo, if that's possible. I currently have only "Collaborator" access on `boostorg/spirit`, which has prevented me from adding some features to CI. Furthermore, I'd prefer full control on the new repo to experiment with GitHub features proactively. - If it isn't feasible, please grant at least permissions to: - "Environments" tab - "Deploy keys" tab - "GitHub Apps" tab - The access to "Environments" tab is required for the "deploy" feature of GHA. It is required to host the temporary preview of AsciiDoc contributions per pull-request scope. This request is based on my personal experimentation, where I found the outside collaborators cannot push directly to the "GitHub Pages", thus it is impossible to host a fully featured preview site on pull-request scope. - I'm planning to add some local bot that alerts compiler warnings in our CI. I need "Deploy keys" and "GitHub Apps" for that. ---------------------------------------------------------- On a personal note, I'm both technically and emotionally satisfied with this direction. Launching Spirit.X4 will let us safely deprecate obsolete features. I'll start by revising the README to document X4's deprecation policy, minimum supported toolchains, and related details. Thank you to everyone involved in the discussion. The encouragement from core devs reinforces my impression that Boost is moving in a constructive and inclusive direction.