On Tue, Jun 2, 2015 at 11:41 PM, James Armstrong
I send out a little feeler about a month ago for interest in a container library which natively allows users to insert a heterogeneous set of types. After getting some really good feedback, I think I have settled into something that is efficient, has a nice clean interface, and provides some useful capabilities. I am hoping people can take a look at the code, test it out, and provide an additional feedback in terms of interface, implementation, bugs, or additional features/classes that would be useful.
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
Hi, I didn't get into details yet, I have questions: 1. did you consider providing the same containers without asking for types? In most of my usage of such containers I don't know which types will get in in the end because the container is shared between different "modules" all inserting data inside. maybe a heterovector<> type that would take anything would be useful to others too? 2. did you consider other kinds of non-standard containers? I think in the discussion you linked I posted examples of heterogeneous containers I use in production that do not have equivalents in std. From memory: a container of 1 value or none for each type, not more, the type(id) being the key to access the value.