KITFORMA · EDITORIAL ANSWER
Why can return std::move(local) reduce return-value optimization?
KitForma editorial guide. Returning a named local directly can permit named return value optimization. Wrapping it with std::move can prevent that particular optimization rather than improve it.
Step-by-step answer
Returning a named local directly can permit named return value optimization. Wrapping it with std::move can prevent that particular optimization rather than improve it.
Return the local by name when it is the owning result and let applicable elision or implicit move rules apply. Reserve explicit movement for actual transfers that need it. Never return a reference to a local as a supposed copy-saving workaround.
Compare constructor instrumentation and optimized output using the supported standard and compiler. Counts can differ when elision is optional. A micro-example is not a guarantee for all types or allocators; correctness and ownership should remain valid even when an optional optimization does not happen.
Sources and verification
Sources checked:
Scope: This editorial guide is based on the cited sources and tool behavior. A forum question or a query observed for our site does not establish market search volume, low competition, guaranteed rankings or inadequate answers elsewhere.
This editorial answer was prepared by KitForma with AI assistance. It is not presented as a real member question or an independent user review. Check the sources and the result with your own file; report corrections in the discussion.