[steveklabnik]

C++ is not memory safe, and neither is uniq_ptr. Use after move on one causes a segfault. (Actually IIRC it's UB, but it usually manifests as a segfault)

[trimbo]

It looks like clang-tidy just committed a check for this case: https://reviews.llvm.org/D23353

[steveklabnik]

Not exactly this case. From the link:

  > No warnings are emitted for objects of type ``std::unique_ptr`` and
  > ``std::shared_ptr``, as they have defined move behavior.

Regardless, I am happy to see more static checking for C++, and am following the GSL/Core Guidelines closely. It's important work.