From: Beman Dawes (beman_at_[hidden])
Date: 2000-11-06 14:07:58
I believe "any" should be accepted by boost.
The docs would benefit from additional guidance to users:
* What's a simple, compelling example of a problem which class any solves
in better way than alternative solutions?
* When is class any the technique of choice for representing a generic
type? IOW, what problem characteristics indicate class any is the right
tool?
* When is class any NOT the best technique for representing a generic
type? IOW, what problem characteristics indicate class any is the wrong
tool? An inheritance hierarchy with a common base class (or whatever) is
sometimes a better way, but how do you decide?
* Is class any itself CopyConstructible, Assignable, EqualityComparable,
LessThanComparable?
* What Standard Library containers can class any be used in? Is there a
way to have a std::set of any?
* What's the typical sizeof() of an object of class any?
Overall, a nice addition to boost!
--Beman