On Wed, Sep 3, 2025, at 10:36 PM, Andrey Semashev via Boost wrote:
On 3 Sep 2025 23:17, Vinnie Falco wrote:
What do you call the bitset whose size can change yet the capacity of the bitset is fixed at compile time?
Following Boost.Container convention, that would be static_dynamic_bitset, but that sounds silly, so static_bitset.
In counterpoint, Boost.Container also has `flat_map` and friends that take a `AllocatorOrContainer` template argument deciding on the storage. E.g. `bc::flat_set<T, std::less<T>, bc::small_vector<T, 15> >`. I'd prefer `dynamic_bitset<uint16_t, bc::small_vector<uint16_t, 8> >` if possible, preventing a proliferation of storage flavors for the sake of it. Of course, whether this is feasible depends mostly on whether the concerns are (can be) separated. Seth