type_traits, arrays, and cv-qualifications

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-22 01:41:35

The changes I made yesterday to is_POD could (should) easily be generalized
to handle a number of things not currently handled. For example, if I
specialize has_trivial_destructor<T>::value <= true,
has_trivial_destructor<T const>::value is still false. Also
has_trivial_destructor<T[n]>::value is still false. This can have real
impact: for example, the array destructor optimization example from the docs
will fail to optimize everything for 2d arrays of trivially-destructible
types.

There are a number of type properties like is_POD which should probably be
propagated through arrays and cv-qualifications:

has_trivial_xxxx
has_nothrow_xxxx
is_stateless (?)

I'm sure there are others.

Interest?

-Dave

+---------------------------------------------------------------+
                  David Abrahams
      C++ Booster (http://www.boost.org)               O__  ==
      Pythonista (http://www.python.org)              c/ /'_ ==
  resume: http://users.rcn.com/abrahams/resume.html  (*) \(*) ==
          email: david.abrahams_at_[hidden]
+---------------------------------------------------------------+