From ad3d1dc6316472c796d54f8220cc24ceb7ab8174 Mon Sep 17 00:00:00 2001
From: Eliyahu Ravuna <Eliyahu-Ravuna@users.noreply.github.com>
Date: Fri, 2 Oct 2015 15:55:31 +0300
Subject: [PATCH] Change agreed in #253

As agreed in #253, three commits squashed into one.
(Suggested 'return containers by value' example + Title made more concise)
---
 CppCoreGuidelines.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
index f65074b..4692cc8 100644
--- a/CppCoreGuidelines.md
+++ b/CppCoreGuidelines.md
@@ -13065,7 +13065,7 @@ Resource management rule summary:
 * [A "raw" pointer or reference is never a resource handle](#Cr-raw)
 * [Never let a pointer outlive the object it points to](#Cr-outlive)
 * [Use templates to express containers (and other resource handles)](#Cr-templates)
-* [Return containers by value (relying on move for efficiency)](#Cr-value-return)
+* [Return containers by value (relying on move or copy elision for efficiency)](#Cr-value-return)
 * [If a class is a resource handle, it needs a constructor, a destructor, and copy and/or move operations](#Cr-handle)
 * [If a class is a container, give it an initializer-list constructor](#Cr-list)
 
@@ -13186,7 +13186,7 @@ Most compilers already warn about simple cases and has the information to do mor
     	int sz;
     };
 
-### <a name="Cr-value-return"></a> Return containers by value (relying on move for efficiency)
+### <a name="Cr-value-return"></a> Return containers by value (relying on move or copy elision for efficiency)
 
 ##### Reason
 
@@ -13194,7 +13194,12 @@ Most compilers already warn about simple cases and has the information to do mor
 
 ##### Example
 
-    ??? vector
+    vector<int> get_large_vector()
+    {
+        return ...;
+    }
+    
+    auto v = get_large_vector(); //return by value is ok, most modern compilers will do copy elision
 
 ##### Example