The author discusses the use of a code optimization technique called copy elision in the context of C++. They highlight how copy elision can interfere with escape analysis, leading to unnecessary code generation. The author provides examples and compares the behavior of different compilers. They also mention a proposal to simplify the language specifications regarding “implicit move” and suggest tightening the object model to allow for more aggressive escape analysis. The author emphasizes that the scenario discussed in the post is rare and not representative of copy elision being a bad technique. Instead, it serves as an interesting piece of trivia and highlights potential areas of improvement in the C++ language.
https://quuxplusone.github.io/blog/2021/03/07/copy-elision-borks-escape-analysis/