simplify push_back logic

[unixnme]

Hello boost devs/maintainers,

I find the current push_back logic a bit strange with the two-steps

• call resize() method but using the default value = false
• then call set() method to explicitly set the bit

I feel it would make sense to simplify this with a single step and reduce overhead

• call resize() method with the given bit

I'm not sure if this is intended, but if not, here is my pull request to address the issue.

Thanks.

[jeking3]

Please rebase this on the current develop branch so that we can run the full set of tests against it. Thanks.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.53%. Comparing base (d4be7a4) to head (237dafa).
Report is 22 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop      #71      +/-   ##
===========================================
- Coverage    95.80%   95.53%   -0.28%     
===========================================
  Files            5        5              
  Lines          668      672       +4     
  Branches         0      210     +210     
===========================================
+ Hits           640      642       +2     
- Misses          28       29       +1     
- Partials         0        1       +1     

Files with missing lines	Coverage Δ
include/boost/dynamic_bitset/dynamic_bitset.hpp	95.19% <100.00%> (-0.30%)	⬇️

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd59d32...237dafa. Read the comment docs.