<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Rvalue-references: how they affect your code</title>
	<link>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/</link>
	<description>Boris Kolpackov's blog about software</description>
	<pubDate>Tue, 14 Apr 2026 08:43:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: pizer</title>
		<link>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-548</link>
		<author>pizer</author>
		<pubDate>Tue, 09 Dec 2008 16:12:16 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-548</guid>
		<description>Nice summarization on move semantics! :)</description>
		<content:encoded><![CDATA[<p>Nice summarization on move semantics! :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Give it a name and its gone &#171; Blockheading about C++</title>
		<link>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-545</link>
		<author>Give it a name and its gone &#171; Blockheading about C++</author>
		<pubDate>Mon, 08 Dec 2008 22:14:13 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-545</guid>
		<description>[...] http://codesynthesis.com/~boris/blog/2008/12/01/rvalue-references-affect-your-code/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] <a href="http://codesynthesis.com/~boris/blog/2008/12/01/rvalue-references-affect-your-code/" rel="nofollow">http://codesynthesis.com/~boris/blog/2008/12/01/rvalue-references-affect-your-code/</a> [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boris Kolpackov</title>
		<link>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-534</link>
		<author>Boris Kolpackov</author>
		<pubDate>Wed, 03 Dec 2008 12:34:05 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-534</guid>
		<description>Hermann,

I think people will learn rvalue-references because they allow writing more efficient and more natural code. As I explained above, none of the approaches used currently are as efficient as return by value of an rvalue-optimized type.

As for letting the compiler do things automatically, I agree it would have been better. However, C++ has a very transparent and unrestrictive object model and doing something "smart" under the hood usually becomes observable in one way or the other. The C++ compiler will do things automatically when rvalues are involved. std::move is just an extra tool that allows you to eliminate copying when lvalues are involved.

Boris</description>
		<content:encoded><![CDATA[<p>Hermann,</p>
<p>I think people will learn rvalue-references because they allow writing more efficient and more natural code. As I explained above, none of the approaches used currently are as efficient as return by value of an rvalue-optimized type.</p>
<p>As for letting the compiler do things automatically, I agree it would have been better. However, C++ has a very transparent and unrestrictive object model and doing something &#8220;smart&#8221; under the hood usually becomes observable in one way or the other. The C++ compiler will do things automatically when rvalues are involved. std::move is just an extra tool that allows you to eliminate copying when lvalues are involved.</p>
<p>Boris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hermann</title>
		<link>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-532</link>
		<author>Hermann</author>
		<pubDate>Wed, 03 Dec 2008 00:51:24 +0000</pubDate>
		<guid>https://codesynthesis.com/~boris/blog//2008/12/01/rvalue-references-affect-your-code/#comment-532</guid>
		<description>Honestly I am still believing that is definitely better to let the compiler know about such optimization than forcing the user to learn a new function to provide some additional efficiency.

Letting the user know about the std::move function will not help C++ become easier. In fact, I think that the difficulty of the usage of this new "keyword" will not stimulate its adoption: why should everyone learn a new trick if the result and compilation is the same of using the previous approaches?

By the way, nice explanation about this new feature. Really! :)

Regards.</description>
		<content:encoded><![CDATA[<p>Honestly I am still believing that is definitely better to let the compiler know about such optimization than forcing the user to learn a new function to provide some additional efficiency.</p>
<p>Letting the user know about the std::move function will not help C++ become easier. In fact, I think that the difficulty of the usage of this new &#8220;keyword&#8221; will not stimulate its adoption: why should everyone learn a new trick if the result and compilation is the same of using the previous approaches?</p>
<p>By the way, nice explanation about this new feature. Really! :)</p>
<p>Regards.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
