gracicot @discuss.tchncs.de
Posts 2
Comments 2
The move constructor that you have to declare, even though you don't want anyone to actually call it - The Old New Thing 3 0
This is actually what I did. I declared it and left a comment to explain why it needed to be left unimplemented.
Reply
The move constructor that you have to declare, even though you don't want anyone to actually call it - The Old New Thing 1 0
I think compiler move return value by default, so even without NRVO you should never move a return value when it's a local non reference variable.
Reply
devblogs.microsoft.com The move constructor that you have to declare, even though you don't want anyone to actually call it - The Old New Thing
Forcing named return value optimization.
![The move constructor that you have to declare, even though you don't want anyone to actually call it - The Old New Thing](https://discuss.tchncs.de/pictrs/image/8dd1bfb4-5532-4ccf-acf8-c280bf523961.jpeg?format=webp&thumbnail=256)
herbsutter.com Trip report: Summer ISO C++ standards meeting (Varna, Bulgaria)
Minutes ago, the ISO C++ committee finished its meeting in-person in Varna, Bulgaria and online via Zoom, where we formally began adopting features into C++26. Our hosts, VMware and Chaos, arranged…
![Trip report: Summer ISO C++ standards meeting (Varna, Bulgaria)](https://discuss.tchncs.de/pictrs/image/1cfcff59-4e66-4416-b327-66ac2e811ff3.png?format=webp&thumbnail=256)
Next