Previously, the signature of a `MultiFunction` was always embedded into the function. There are two issues with that. First, `MFSignature` is relatively large, because it contains multiple strings and vectors. Secondly, constructing it can add overhead that should not be necessary, because often the same signature can be reused. The solution is to only keep a pointer to a signature in `MultiFunction` that is set during construction. Child classes are responsible for making sure that the signature lives long enough. In most cases, the signature is either embedded into the child class or it is allocated statically (and is only created once). |
||
---|---|---|
.. | ||
cpp_types.cc | ||
generic_vector_array.cc | ||
generic_virtual_array.cc | ||
generic_virtual_vector_array.cc | ||
multi_function.cc | ||
multi_function_builder.cc | ||
multi_function_network.cc | ||
multi_function_network_evaluation.cc | ||
multi_function_network_optimization.cc |