upgrade to a more recent version of boost
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 492
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
The version of Boost currently in use by this library is 1.72.0-p1, which is over a year and a half old. FWIW, I've had no issue compiling it with newer versions of Boost--and hadn't even noticed you had locked in such an old version, as I don't use cmake/hunter--until this week, with the release of 1.76.0, which finally removed support for the apparently-long-deprecated older way of using Boost Outcome's macros.
https://www.boost.org/doc/libs/develop/libs/outcome/doc/html/changelog/upgrade_v21_v22.html
As cmake/hunter has in fact been updating to more recent versions of Boost as they come out, I'm honestly not sure exactly what is holding back the version being used by this project (this seems like some kind of secret decision being made by cmake hunter somewhere, maybe due to something buried in a dependency... not that I've so far found anything that looks like such anywhere in any of these projects).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the CMake/Hunter dependency configuration that pins Boost at 1.72.0-p1, then compare it with the Boost Outcome 1.76.0 upgrade notes linked in the issue. Done means the project uses a newer Boost version without breaking its build or Boost Outcome macro usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100