- Helper function to find out of two objects are located "close to each other" -- which can be used as heuristics to distinguish heap vs. stack storage - further investigation shows that libstdc++ applies the small-object optimisation for functor up to »two slots« in size -- but only if the copy-ctor is trivial. Thus a lambda capturing a shared_ptr by value will *always* be maintained in heap storage (and LazyInit must be redesigned accordingly)... - the verify_inlineStorage() unit test will now trigger if some implementation does not apply small-object optimisation under these minimal assumptions |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||