10 ms·
TFA explains how std::move is tricky to use and this is not a feature reserved for library writers
by yosefk 9mo ago
TFA explains how std::move is tricky to use and this is not a feature reserved for library writers
- zabzonk 9mo agoOf course it is not reserved for library writers - nothing is. But it is not a feature that application writers should worry about overmuch.
- yosefk 9mo agostd::move is definitely for there for optimizing application code and is often used there. another silly thing you often see is people allocating something with a big sizeof on the stack and then std::moving it to the heap, as if it saves the copying
- zabzonk 9mo ago> another silly thing you often see is people allocating something with a big sizeof on the stack and then std::moving it to the heap, as if it saves the copying never seen this - an example?