TR library extensions

[Matt Austern]

As most of you probably know, the standardization committee is working 
on a technical report on standard library extensions.  Basically it 
just specifies a whole lot of stuff that might be added to a future 
version of the standard someday.  Standard library implementers are 
encouraged to supply these things as extensions, so they and their 
users can experiment when them.  (They're supposed to go in std::tr1, 
not in std, since they aren't yet part of the standard and might never 
be.)

A draft version of the TR is available at 
<http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1518.pdf>.

We aren't supplying any of the TR extensions yet.  I think we should.  
Doing all of it will be tremendously hard (one of the components 
requires serious numerical work), but we should at least start on it so 
we have a framework for contributions.

What do people think about directory structure and naming conventions 
and such?

			--Matt