https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82610
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Sorry about the breakage. (In reply to Richard Biener from comment #1) > Hmm, include/ shouldn't include system headers directly :/ Of course they > all do... > > <memory> is probably not too bad to include unconditionally, but maybe we > can avoid including that for unique-ptr.h? Quickly browsing doesn't find > anything > needing it? Nothing is using gnu::unique_ptr currently, but I hope to start using it in e.g.: https://gcc.gnu.org/ml/gcc-patches/2017-10/msg01021.html On C++-11 and beyond that's std::unique_ptr, and hence <memory> would be needed.
