Squashed 'third_party/boostorg/type_traits/' content from commit 059ed88
Change-Id: I222c604dfa1db194bf53bc6aa1152fb16e83ce06
git-subtree-dir: third_party/boostorg/type_traits
git-subtree-split: 059ed8839da3fecd1e8b62cdc11be006f6346b5e
diff --git a/doc/is_nothrow_move_assignable.qbk b/doc/is_nothrow_move_assignable.qbk
new file mode 100644
index 0000000..782f2c4
--- /dev/null
+++ b/doc/is_nothrow_move_assignable.qbk
@@ -0,0 +1,34 @@
+[/
+ Copyright 2007 John Maddock.
+ Copyright 2013 Antony Polukhin.
+ Distributed under the Boost Software License, Version 1.0.
+ (See accompanying file LICENSE_1_0.txt or copy at
+ http://www.boost.org/LICENSE_1_0.txt).
+]
+
+[section:is_nothrow_move_assignable is_nothrow_move_assignable]
+
+ template <class T>
+ struct is_nothrow_move_assignable : public __tof {};
+
+__inherit If `T` is a (possibly cv-qualified) type with a non-throwing move assignment-operator
+or a type without move assignment-operator but with non-throwing assignment-operator,
+then inherits from __true_type, otherwise inherits from __false_type. Type `T`
+must be a complete type.
+
+In other words, inherits from __true_type only if expression `variable1 = std::move(variable2)`
+won't throw (`variable1` and `variable2` are variables of type `T`).
+
+__compat If the compiler does not support partial-specialization of class
+templates, then this template can not be used with function types.
+
+Without some (C++11 noexcept shall work correctly) help from the compiler,
+`is_nothrow_move_assignable` will never report that a class or struct has a
+non-throwing assignment-operator; this is always safe, if possibly sub-optimal.
+Currently (June 2015) MSVC-12.0, Clang and GCC 4.7 have the necessary compiler support to ensure that this
+trait "just works".
+
+__header ` #include <boost/type_traits/is_nothrow_move_assignable.hpp>` or ` #include <boost/type_traits.hpp>`
+
+[endsect]
+