StarMirror/CppCoreGuidelines
1
0
Fork 0
mirror of https://github.com/isocpp/CppCoreGuidelines.git synced 2024-03-22 13:30:58 +08:00
Code Issues Projects Releases Wiki Activity

Change agreed in #253

Browse Source 
As agreed in #253, three commits squashed into one.
(Suggested 'return containers by value' example + Title made more concise)
This commit is contained in:
Eliyahu Ravuna 2015-10-02 15:55:31 +03:00
parent f3780fa74b
commit ad3d1dc631
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
CppCoreGuidelines.md
View File

@ -13065,7 +13065,7 @@ Resource management rule summary:
* [A "raw" pointer or reference is never a resource handle](#Cr-raw) * [A "raw" pointer or reference is never a resource handle](#Cr-raw)
* [Never let a pointer outlive the object it points to](#Cr-outlive) * [Never let a pointer outlive the object it points to](#Cr-outlive)
* [Use templates to express containers (and other resource handles)](#Cr-templates) * [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 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) * [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; 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 ##### Reason
@ -13194,7 +13194,12 @@ Most compilers already warn about simple cases and has the information to do mor
##### Example ##### 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 ##### Example