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

improve I.11

Browse Source 
as suggested in #552
This commit is contained in:
Bjarne Stroustrup 2017-05-17 14:41:53 -04:00
parent fa1d0e5995
commit 974fdf4661
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
CppCoreGuidelines.md
View File

@ -1788,8 +1788,9 @@ Consider returning the result by value (use move semantics if the result is larg
return res; return res;
} }
**Alternative**: Pass ownership using a "smart pointer", such as `unique_ptr` (for exclusive ownership) and `shared_ptr` (for shared ownership). **Alternative**: [Pass ownership](#Rr-smartptrparam) using a "smart pointer", such as `unique_ptr` (for exclusive ownership) and `shared_ptr` (for shared ownership).
However, that is less elegant and less efficient unless reference semantics are needed. However, that is less elegant and often less efficient than returning the object itself,
so use smart pointers only if reference semantics are needed.
**Alternative**: Sometimes older code can't be modified because of ABI compatibility requirements or lack of resources. **Alternative**: Sometimes older code can't be modified because of ABI compatibility requirements or lack of resources.
In that case, mark owning pointers using `owner` from the [guideline support library](#S-gsl): In that case, mark owning pointers using `owner` from the [guideline support library](#S-gsl):
@ -1813,7 +1814,7 @@ caller, so that its lifetime is handled by the caller. Viewed another way:
ownership transferring APIs are relatively rare compared to pointer-passing APIs, ownership transferring APIs are relatively rare compared to pointer-passing APIs,
so the default is "no ownership transfer." so the default is "no ownership transfer."
**See also**: [Argument passing](#Rf-conventional) and [value return](#Rf-T-return). **See also**: [Argument passing](#Rf-conventional), [use of smart pointer arguments](#Rr-smartptrparam), and [value return](#Rf-T-return).
##### Enforcement ##### Enforcement