<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in coroutine-no-move-ctor.cpp</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>d30ca5e2 - [C++20] [Coroutines] Implement return value optimization for get_return_object</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/SemaCXX/coroutine-no-move-ctor.cpp#d30ca5e2</link>
        <description>[C++20] [Coroutines] Implement return value optimization for get_return_objectThis patch tries to implement RVO for coroutine&apos;s return object got fromget_return_object.From [dcl.fct.def.coroutine]/p7 we could know that the return value ofget_return_object is either a reference or a prvalue. So it makes senseto do copy elision for the return value. The return object should beconstructed directly into the storage where they would otherwise becopied/moved to.Test Plan: folly, check-allReviewed By: junparserDifferential revision: https://reviews.llvm.org/D117087

            List of files:
            /llvm-project-15.0.7/clang/test/SemaCXX/coroutine-no-move-ctor.cpp</description>
        <pubDate>Mon, 10 Jan 2022 11:18:33 +0000</pubDate>
        <dc:creator>Chuanqi Xu &lt;yedeng.yd@linux.alibaba.com&gt;</dc:creator>
    </item>
</channel>
</rss>
