Gennaro Prota 41799d3fe5 Take into account that the underlying container is not necessarily a std::vector in max_size() ...

The vector_max_size_workaround() we had in place, and one of the test
cases, only considered std::vectors, which are no longer the only
allowed containers. This commit fixes "Allow choosing the underlying
container type".

2025-10-15 11:41:44 +02:00

..

cmake_test

GHA: Add CMake subdir test

2024-11-26 12:14:09 -05:00

bitset_test.hpp

Take into account that the underlying container is not necessarily a std::vector in max_size()

2025-10-15 11:41:44 +02:00

dyn_bitset_unit_tests1.cpp

Take into account that the underlying container is not necessarily a std::vector in max_size()

2025-10-15 11:41:44 +02:00

dyn_bitset_unit_tests2.cpp

Add some missing const qualifiers

2025-10-15 11:41:44 +02:00

dyn_bitset_unit_tests3.cpp

Add some missing const qualifiers

2025-10-15 11:41:44 +02:00

dyn_bitset_unit_tests4.cpp

Assume locales and std::use_facet() are always available

2025-10-15 11:41:44 +02:00

dyn_bitset_unit_tests5.cpp

Assume locales and std::use_facet() are always available

2025-10-15 11:41:44 +02:00

Jamfile.v2

Update build deps.

2024-11-24 06:48:02 -05:00

test_ambiguous_set.cpp

Remove a few unneeded permission notices

2025-10-14 19:24:45 +02:00

test_boost_hash.cpp

Remove a few unneeded permission notices

2025-10-14 19:24:45 +02:00

test_lowest_bit.cpp

Remove a few unneeded permission notices

2025-10-14 19:24:45 +02:00

test_std_hash.cpp

Also test std::hash with bitsets having equal underlying vectors

2025-10-15 11:41:44 +02:00