> > The memory pool design makes some tradeoffs. It is not meant to > be completely replace malloc / free as a general purpose > allocator, but rather used in scenarios where the benefit (faster > allocations, lower bookkeeping overhead) is worth the > tradeoffs (not able to free individual allocations). So this is the actual stated design goal of this memory pool? Fast&cheap allocation with little overhead for giving up individual frees? > We debated several approaches for what to do here it would be awesome if the list could participate in the discussion even if only read-only.
