Repository navigation
Remove Boost.StaticAssert submodule #19
Copy link
Copy link
Open
Description
Since Boost.StaticAssert has been merged into Boost.Config, this submodule can be removed once all Boost libraries have removed references to it. For tracking purposes, here is the list of the relevant PRs:
-
Remove dependencies on Boost.StaticAssert callable_traits#201
-
Remove dependencies on Boost.StaticAssert circular_buffer#54
-
Remove dependencies on Boost.StaticAssert program_options#155
-
Remove dependencies on Boost.StaticAssert property_map_parallel#4
Once these PRs are merged and propagate to master, I propose to add a release note for the next Boost release to notify users that the submodule is deprecated and will soon be removed. Then, after 3 Boost releases, actually remove the submodule.
CC @pdimov
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
pdimov commentedon Jan 22, 2026
No, I don't think we should remove it. This will break way too much stuff.
Lastique commentedon Feb 2, 2026
@pdimov Could you please merge PRs for other libraries, at least the unmaintained and widely used ones? Assign, CircularBuffer, ConceptCheck, Config, Contract, Compute, MPL, PropertyMap, Proto, Range, TypeOf, Variant seem to be ready for merge, and other libraries may be enabled by these (especially, ConceptCheck and MPL).
pdimov commentedon Feb 3, 2026
I've added you to the community maintenance team, which should give you access to some of these.
Lastique commentedon Feb 3, 2026
Thanks. I've merged what I could, the rest are still out of my reach.
pdimov commentedon Feb 3, 2026
You'll need to merge to master as well, because I'm getting https://github.com/boostorg/circular_buffer/actions/runs/21631032975/job/62343535609
Lastique commentedon Feb 3, 2026
I've merged to master.
Lastique commentedon Feb 4, 2026
Could you please merge PRs for Accumulators, Algorithm, Chrono, Contract, DateTime, FunctionTypes, MultiArray, PropertyTree, Thread, Variant, Xpressive? I'm not sure if Range and Serialization are actively maintained, so maybe those too.
pdimov commentedon Feb 4, 2026
Variant should be actively maintained, but I'll handle the rest.
pdimov commentedon Feb 6, 2026
I've merged Accumulators, Chrono, FunctionTypes, Xpressive. Algorithm seems maintained by @mclow.
pdimov commentedon Feb 6, 2026
It takes longer than expected because I use this opportunity to fix or add CI.
Contract, DateTime merged as well; CI seems up to date there.
I've given you write access to MultiArray because it seems unmaintained and I see you have a pending PR there.
pdimov commentedon Feb 6, 2026
Gave you access to PropertyTree as well.
pdimov commentedon Feb 6, 2026
And Thread while we're at it.
Lastique commentedon Feb 6, 2026
Thanks, I've merged MultiArray, PropertyTree and Thread. Is there anything else you think you could merge?
pdimov commentedon Feb 6, 2026
The remaining ones from your list above are Variant, Range, Serialization, and all have active maintainers if I'm not mistaken.
Lastique commentedon Feb 6, 2026
I listed the PRs for libraries that I considered low-level and not actively maintained. At this point, the unmerged PRs are:
[*] In the above, I'm not considering Drone CI as it is inaccessible in my region and right now I can't view it.
If my analysis is correct, it is worth looking at Compute, GraphParallel, Range, Serialization, UBLAS, Units.
e-kwsm commentedon Apr 9, 2026
This repo can be archived?