Swap and move boost::pool
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the boost::pool implementation and its current ownership and lifetime behavior. Define the expected swap and move semantics for pool instances, then identify how those semantics should be validated. Done means the requested operations have clear behavior and coverage for the stated object-owning use case.
Written by the indexing model from the issue text.
Description
Hello,
from a quick look (so I can easily be mistaken) at the implementation of boost::pool, it looks like allowing swap and move operations should not cause any major issue. Is that something that you would consider?
Use case: we do not use a global pool (bad for threading), we have a few big objects (usually no more than a handful, or maybe 1-2 per thread) that each own a pool for their internal needs, and we would like to provide swap/move operations on those objects. Wrapping the pool in a unique_ptr is a possibility, but it seems like an unnecessary (small) waste.
- Dominant language
- C++
- Stars
- 58
- Forks
- 52
- 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/pool
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
EchoTools/nevr-runtime#116 ·
Maintainers usually reply within 1 day
-
code-quality libc++
Difficulty 1/5 Under an hour Newbie friendliness 82/100
llvm/llvm-project#229284 ·
Maintainers usually reply within 1 day
-
test-issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
llvm/offload-test-suite#1557 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day