I'd like to announce the beginning of the review of the Heap library,
I have a couple of issues that I'd like to see addressed, but I'd like to discuss them rather than just noting them in the review app.
One of my primary objections to the current design is the use of unspecified policy parameters in the template parameter list of the main data structures. I think that it is important to limit the number of top-level template parameters to only non-policy parameters.
of course this can be discussed ... i somehow like this explicit way of specifying parameters, but this is probably my personal preference ... i think it would be great to have a clear policy among all (or all new) boost libraries ... then this can be discussed once and only once ... i would prefer to have clear interface guidelines instead of arguing about personal preferences :)
Second, it protects the template interface from later design decisions. For example, if you accept Thorstens recommendation to parameterize over the container type, you don't have to add a new top-level template parameter; you would only have to modify the default policies and the metafunctions that query for it.
... i haven't really worked with c++0x, yet ... but isn't this address by variadic templates? cheers, tim