What
Generate static conveniences for trait accessors/mutators, such that the (C++) refcount of the TraitsData is not modified.
Why
C++ purists will balk at wrapping a TraitsData in a short-lived trait view to operate on it, likely necessitating a shared_ptr copy and refcount bump. This is a potentially measurable performance hit in large-volume operations.
E.g. we can add static variants such as getLocationFrom(const TraitsData&), and similarly setLocationTo.
What
Generate
staticconveniences for trait accessors/mutators, such that the (C++) refcount of theTraitsDatais not modified.Why
C++ purists will balk at wrapping a
TraitsDatain a short-lived trait view to operate on it, likely necessitating ashared_ptrcopy and refcount bump. This is a potentially measurable performance hit in large-volume operations.E.g. we can add
staticvariants such asgetLocationFrom(const TraitsData&), and similarlysetLocationTo.