Here the design trardeoff becomes clearly visiblie - on the plus side, we removed that spurous redundant info from the template parameter, and we simplified functor rebinding - but as a tradeoff, we now always have two std::function objects nested into each other, which also means that at least the outer object resides on the heap and /inevitably/ calls through a function pointer, even in case the target function is a lambda, simply because some type erasure happened, and the call site does not know the actual type anymore |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||