Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Comparison of C++17, Go, and Java for a next-generation sequencing tool. Parent comment
Chandler Carruth talks about this at CppCon 2019 [0]. From a quick review he says part of the reason std::unique_ptr isn't zero-cost right now is:
- Objects passed by value (like std::unique_ptr) are passed on the stack instead of in registers, and changing that will be an ABI break
- No destructive move means extra temporaries will be created/retained
[0]: https://youtu.be/rHIkrotSwcc?t=1046
There are no comments on this comment yet.
Chandler Carruth talks about this at CppCon 2019 [0]. From a quick review he says part of the reason std::unique_ptr isn't zero-cost right now is:
- Objects passed by value (like std::unique_ptr) are passed on the stack instead of in registers, and changing that will be an ABI break
- No destructive move means extra temporaries will be created/retained
[0]: https://youtu.be/rHIkrotSwcc?t=1046