Merge Assert, StaticAssert, ThrowException into Core
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
Research direction
Start by reviewing the listed headers in boost/static_assert.hpp, boost/assert.hpp, boost/current_function.hpp, boost/assert/source_location.hpp, boost/throw_exception.hpp, and boost/exception/exception.hpp, along with their Config dependencies. Compare the documentation formats referenced in the issue. Done means the four dependencies are consolidated into Core while accounting for the documented library impact.
Written by the indexing model from the issue text.
Description
Recently Core grew with additional dependencies on StaticAssert (in 1.76) and ThrowException (in the next release), previously it was only depending on Assert and Config. That made a lot of libraries checkout the same four repositories, three of them containing only a few headers. Merging into a single dependency will affect mostly positive about 100 libraries and negative 1: StlInterfaces (depends on Assert, and will on Core).
There is some difference in documentation format used (https://github.com/boostorg/core/commit/95924b1329da49e70c9c8485b87e066895db2d64#r58137316), but that should be solvable.
Headers list:
StaticAssert (depends on Config)
- boost/static_assert.hpp
Assert (depends on Config)
- boost/assert.hpp
- boost/current_function.hpp
- boost/assert/source_location.hpp
ThrowException (depends on Assert and Config)
- boost/throw_exception.hpp
- boost/exception/exception.hpp
- Dominant language
- C++
- Stars
- 156
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from boostorg/core
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
saturate_castOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
move span to boost::core::May be free again @glenfe claimed this 493 days ago, and no pull request is open. Open
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ROCm/rocm-systems#12638 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Ryan-Millard/Img2Num#652 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
lxqt/qtermwidget#688 ·
Maintainers usually reply within 1 day
-
CI enhancement tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lfortran/lfortran#13885 · 1 comment ·
Maintainers usually reply within 1 day