Deallocation in pool resources
(too old to reply)
2018-11-01 04:13:15 UTC
AFAIK, [mem.res.pool] does not specify when to deallocate the free chunks
to make them back to the upstream resource besides release() and
destruction of the whole resource object. So a monotonic implementation
which never gives back free blocks before release() or destruction call is
conforming. As a consequence, besides deallocation of all allocated blocks,
there is no portable way to avoid the monotonic behavior when it is not
desired. Is this really intended, or have I missed something obvious?
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-discussion+***@isocpp.org.
To post to this group, send email to std-***@isocpp.org.
Visit this group at https://groups.google.com/a/isocpp.org/group/std-discussion/.
Continue reading on narkive: