From 863580fe881c32af82eb106817e71dc560d9e775 Mon Sep 17 00:00:00 2001 From: Gael Guennebaud Date: Wed, 18 Jul 2018 23:33:07 +0200 Subject: bug #1432: fix conservativeResize for non-relocatable scalar types. For those we need to by-pass realloc routines and fall-back to allocate as new - copy - delete. The remaining problem is that we don't have any mechanism to accurately determine whether a type is relocatable or not, so currently let's be super conservative using either RequireInitialization or std::is_trivially_copyable --- test/AnnoyingScalar.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test/AnnoyingScalar.h') diff --git a/test/AnnoyingScalar.h b/test/AnnoyingScalar.h index 08854a114..b5b1476fe 100644 --- a/test/AnnoyingScalar.h +++ b/test/AnnoyingScalar.h @@ -22,7 +22,7 @@ struct my_exception // An AnnoyingScalar is a pseudo scalar type that: // - can randomly through an exception in operator + -// - randomly allocate on the heap or initialize a reference to itself making it non trivially copyable, nor movable. +// - randomly allocate on the heap or initialize a reference to itself making it non trivially copyable, nor movable, nor relocatable. class AnnoyingScalar { -- cgit v1.2.3