2 ms·
My point is that you would use boost.container if you need its additional features otherwise just use the equivalent standard containers. The complexity is ther
by gpderetta 6y ago
My point is that you would use boost.container if you need its additional features otherwise just use the equivalent standard containers. The complexity is there for a reason.
A separate .cpp would require explicit instantiation. I do not see how that would work for a third party library that has to work for any T.
Normally you can at least abstract away the memory management code, but in the case of boost container the use of custom allocators is expected, so you can't even do that.