With recent compilers, the optimizations are terrific, so it may be best to let the compiler do it without having to do the risky optimization yourself.
For example, the following code, seems inefficient, but the compiler optimization expands the constructor on the returned object. It doesn’t bother to create an object on the stack and then “pass by value” to the return value.
|
1 2 3 4 5 6 7 |
CHash create_sha256() { CHash obj; obj.algo = CHash::ALGO::SHA256; return obj; } CHash hash = create_sha256(); |
When “pass by reference” becomes available, they seem to think that this is an efficient way. However, if you can get the same optimization with safe “pass by value”, you should use “pass by value”.
