http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58407
--- Comment #7 from Andrzej Krzemienski <akrzemi1 at gmail dot com> --- Just one remark. A warning in this situation is not to just warn about any deprecated feature, but to indicate something that is very likely to be a bug (It used to be legal in C++03, so you couldn't legally warn about it; now the deprecation is just an additional incentive). My guess is that having this copy constructor implicitly defined when you have a custom destructor is a potential bug in half of the cases. (Well, "half" is my guess.)
