2 Dec
2014
2 Dec
'14
5:23 p.m.
Update: in the absence of SFINAE expression support, a number of type_traits are terminally broken, and this is one I'm afraid.
If this is unimplementable, then that's fine. What I find confusing is that regression tests for is_nothrow_move_assignable pass on this compiler: http://www.boost.org/development/tests/develop/developer/type_traits.html
The compiler has an __is_nothrow_assignable() built-in, which seems usable here.
The standard says that is_nothrow_move_assignable<T> is the same as is_nothrow_assignable
.
Will investigate. BTW the current implementation does use noexcept - the issue is that in some situations this leads to noexcept(expression-that-doesn't-compile) which requires SFINAE-expression support. John.