Notably this raises the difficult question, whether to ensure **invocation of destructors**. Not invoking dtors ''breaks one of the most fundamental contracts'' of the C++ language — yet the infrastructure to invoke dtors in such a heterogeneous cluster of allocations creates a hugely significant overhead and is bound to poison the caches (objects to be deallocated typically sit in cold memory pages). What makes this decision especially daunting is the fact that the low-level-Model can be expected to be one of the largest systemic data structures (letting aside the media buffers). I am leaning towards a compromise: turn down this decision towards the user of the `AllocationCluster` |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| dump | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||