Mirrors/cppbestpractices
1
0
Fork 0
mirror of https://github.com/cpp-best-practices/cppbestpractices.git synced 2025-12-17 03:04:36 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add note about const & vs return by value

Browse Source 
Closes #21
This commit is contained in:
Jason Turner
2015-07-17 18:36:39 -06:00
parent 070d3e7d39
commit bcc650ae05
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
04-Considering_Safety.md
View File

@@ -43,6 +43,12 @@ private:
}
```
### Consider Return By Value for Mutable Data, `const &` for Immutable
You don't want to have to pay a cost for copying the data when you don't need to, but you also don't want to have to safely return data in a threading scenario.
See also this discussion for more information: https://github.com/lefticus/cppbestpractices/issues/21
## Avoid Raw Memory Access
Raw memory access, allocation and deallocation, are difficult to get correct in C++ without [risking memory errors and leaks](http://blog2.emptycrate.com/content/nobody-understands-c-part-6-are-you-still-using-pointers). C++11 provides tools to avoid these problems.