[ This may require a new Comments column ]

has_nothrow_default_constructor
has_nothrow_copy_constructor
has_nothrow_assign

Proposed resolution:

Add the following comment:

user specialization permitted to derive from std::true_type when the operation is known not to throw.

to the following traits in [meta.unary.prop] Table 43 Type property predicates.

Rationale:

We believe the solution offered by N3050 is superior.

[ 2010 Pittsburgh: Moved to NAD, rationale added below. ]

[ 2009-10 Santa Cruz: ]

Moved to Open. Definitely need to give the users the ability to ensure that the traits give the right answers. Unsure we want to give them the ability to say this in more than one way. Believes the noexcept proposal already gives this.

According to p1 [meta.type.synop]:

The behavior of a program that adds specializations for any of the class templates defined in this subclause is undefined unless otherwise specified.

I believe we should 'otherwise specify' for the nothrow traits, are these are exactly the use cases where the end user actually has more information than the compiler.