From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-11-26 10:35:49
----- Original Message -----
From: "Hamish Mackenzie" <boost_at_[hidden]>
> This would simplify using tuples and I can't think of a good argument
> not to do it. It would however, mean that tuples and type_lists would be
> forever linked. Can anyone think of a reason we might want more than
> one tuple type?
Yes: one might want to use one's tuple metaprogramming libraries on a tuple
type supplied by some 3rd-party library. The MPL provides a traits-based
mechanism which allows any number of different type lists to be used with
its algorithms. A similar approach could be taken for tuples.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk