One shouldn't std::move in a return. Returning a local is already automatically ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		dearrifling on April 23, 2019 \| parent \| context \| favorite \| on: Modern C++ Won't Save Us One shouldn't std::move in a return. Returning a local is already automatically an rvalue, however explicitly moving it disables copy elision.

petters on April 23, 2019 [–]

You are completely right. That should be fixed

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact