On June 2, 2015 5:41:04 PM EDT, James Armstrong
I have implemented a set of containers which mimic the capabilities of the STL containers. These are (so far)
* heterovector * heterostack * heteroqueue * heterolist * heteroforward_list * heterodeque
Why do you have both a namespace and a "hetero" prefix? That's redundant. I cannot imagine a use case for any of these. Rather than have a set of containers, each targeted to a specific data type, your interface uses one type that must be specialized in every use, including member function calls. The former does require naming each container, but that leads to more readable, simpler code in my mind. Can you provide any motivating examples for using these containers which demonstrate their benefits over ad hoc containers?
In addition, I have an adaptor class which provides a simple interface for accessing data of a specific type from a container of type_erased objects (boost::any, boost::variant, etc).
This class seems to provide a little syntactical sugar over an any-based container, so I can imagine some benefit. ___ Rob (Sent from my portable computation engine)