[Boost-users] [Review] The 'Type Traits Introspection' library Review starst next friday, july 1st

Subject: [Boost-users] [Review] The 'Type Traits Introspection' library Review starst next friday, july 1st
From: Joel falcou (joel.falcou_at_[hidden])
Date: 2011-06-24 12:55:51

According to the schedule, review for the Type Traits Introspection 
library by Edward Diener will run from friday, July 1st to monday, july 
10 2011.

===========
What is it?
===========

The TTI library, which is an abbreviation for the 'Type Traits 
Introspection' library, allows a programmer to introspect at compile 
time the inner elements of a C++ type. The introspection process depends 
on specifying the name of the inner element by different macros for 
different types of elements, and then using a generated metafunction to 
determine whether that element exists within the enclosing type. The 
inner elements which can be introspected are type, class template, 
member data, member function, static member data, and static member 
function.

The TTI library is based on the type_traits_ext portion of the Concept 
Traits Library, with improvements and additions, and also reproduces 
functionality ( without changing existing code ), for the purposes of 
completeness, from Boost.MPL regarding introspection of types and templates.

The purpose of the library is to provide a consistent set of interfaces 
for doing compile-time introspection of a type, which other template 
metaprogrammers can use in their code. If you are at all interested in 
compile-time introspection of types, please take a look at the 
functionality of this library.

===================
Getting the library
===================
The library is available at http://svn.boost.org/svn/boost/sandbox/tti/ 
Note that this repository will be updated up to next thursday by Edward.

===================
   Writing a Review
===================

The reviews and all comments should be submitted to the developers list,
and the email should have "[TTI] Review" at the beginning of the subject 
line to make sure it's not missed.

Please explicitly state in your review whether the library should be
accepted.

The general review checklist:

     - What is your evaluation of the design?
     - What is your evaluation of the implementation?
     - What is your evaluation of the documentation?
     - What is your evaluation of the potential usefulness of the
       library?
     - Did you try to use the library?  With what compiler?  Did you
       have any problems?
     - How much effort did you put into your evaluation? A glance? A
       quick reading? In-depth study?
     - Are you knowledgeable about the problem domain?

And finally, every review should answer this question:

     - Do you think the library should be accepted as a Boost library?

Be sure to say this explicitly so that your other comments don't
obscure your overall opinion.