3 ms·
Its not std::move, but the complexity coming with it. Its a hassle applying move semantics correctly and there is not the one goto solution for simple things.
by cominous 9y ago
Its not std::move, but the complexity coming with it.
Its a hassle applying move semantics correctly and there is not the one goto solution for simple things. Im not aware of a proposal to change that issue, but at least there should be better defaults.
This talk explains the pain quite well:
https://www.youtube.com/watch?v=PNRju6_yn3o https://www.youtube.com/watch?v=PNRju6_yn3o
- repsilat 9y agoThe amount of prayer I have put into RVO and moves happening "right"... As someone who isn't a C++ programmer, is there anything better than looking at annotated asm? Templating everything and trying it with something that isn't copyable? (Actually, would that even work with RVO?)
- jcelerier 9y ago> As someone who isn't a C++ programmer, is there anything better than looking at annotated asm put a debug breakpoint in the move constructor and run your tests :p