# HG changeset patch # User Mike Becker # Date 1744375763 -7200 # Node ID 0c8077f67e54eacf232291e6a3feecc7278b9d7e # Parent 45746a08c59e7104208a04a51cc0a6b78ad89388 remove warning regarding destruction order, because it is actually not a problem relates to #640 diff -r 45746a08c59e -r 0c8077f67e54 docs/Writerside/topics/mempool.h.md --- a/docs/Writerside/topics/mempool.h.md Fri Apr 11 13:20:07 2025 +0200 +++ b/docs/Writerside/topics/mempool.h.md Fri Apr 11 14:49:23 2025 +0200 @@ -75,14 +75,6 @@ or the `source` and `dest` pointers point to the same pool. In case of an error, no memory is transferred and both pools are in a valid state. -> Although the allocator from the `source` pool remains valid for the already allocated objects, -> it is **not** valid to use that allocator to allocate new objects in the `dest` pool. -> It may only be used to free or reallocate the memory of the existing objects. -> -> The reason is, that the allocator will be destroyed after destroying all objects from the `source` pool and -> _before_ destroying objects in the `dest` pool which were allocated after the transfer. ->{style="warning"} - ## Example