Fix has_nothrow_move and avoid boost::has_nothrow_move<copyable>::value test as each compiler can deduce a different thing depending on its type analysis.

[SVN r85410]
2013-08-20 18:10:09 +00:00
parent c07b4d3365
commit 55d5015a2b
2 changed files with 2 additions and 3 deletions
@@ -41,14 +41,14 @@ struct has_trivial_destructor_after_move
 {};

 //! By default this traits returns
-//! <pre>boost::is_nothrow_move_constructible<T>::value || boost::is_nothrow_move_assignable<T>::value </pre>.
+//! <pre>boost::is_nothrow_move_constructible<T>::value && boost::is_nothrow_move_assignable<T>::value </pre>.
 //! Classes with non-throwing move constructor
 //! and assignment can specialize this trait to obtain some performance improvements.
 template <class T>
 struct has_nothrow_move
   : public ::boost::move_detail::integral_constant
      < bool
-      , boost::is_nothrow_move_constructible<T>::value ||
+      , boost::is_nothrow_move_constructible<T>::value &&
        boost::is_nothrow_move_assignable<T>::value
      >
 {};