diff options
author | Casey Carter <cacarter@microsoft.com> | 2023-06-21 17:14:53 -0700 |
---|---|---|
committer | Casey Carter <cacarter@microsoft.com> | 2023-07-24 22:33:40 -0700 |
commit | 07c59eda00841aafaafd8fd648217b56b1e907c9 (patch) | |
tree | 20b3614e414238378396a55083a27a52fd6f49b4 /src/banman.h | |
parent | 6a473373d4953cabbb219eae8b709150a45796e6 (diff) | |
download | bitcoin-07c59eda00841aafaafd8fd648217b56b1e907c9.tar.xz |
Don't derive secure_allocator from std::allocator
Affects both secure_allocator and zero_after_free_allocator.
Giving the C++ Standard Committee control of the public interface of your type means they will break it. C++23 adds a new `allocate_at_least` member to `std::allocator`. Very bad things happen when, say, `std::vector` uses `allocate_at_least` from `secure_allocator`'s base to allocate memory which it then tries to free with `secure_allocator::deallocate`.
Drive-by: Aggressively remove facilities unnecessary since C++11 from both allocators to keep things simple.
Diffstat (limited to 'src/banman.h')
0 files changed, 0 insertions, 0 deletions