Re:C++: Return value optimization vs. std::move
by nly on Monday July 20, 2015 @11:02PM
(#9920349)
Constructors may need to allocate a sentinel, I see no reason for the move constructor to do so. I'd also question the performance benefits of having a sentinel (basically avoiding additional null pointer checks) has on performance given todays relative cache penalties.
[ Parent
| on HN ]
There are no comments on this comment yet.