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

Added link to article from Herb Sutter

Browse Source
This commit is contained in:
Robin Schlegel
2015-06-30 19:53:33 +02:00
parent 51821c8741
commit 9324e48f12
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
07-Considering_Threadability.md
View File

@@ -14,3 +14,5 @@ Much slower in threaded environments. In many or maybe even most cases, copying
For member variables it is good practice to use mutex and mutable together. This applies in both ways: For member variables it is good practice to use mutex and mutable together. This applies in both ways:
* A mutable member variable is presumed to be a shared variable so it should be synchronized with a mutex (or made atomic) * A mutable member variable is presumed to be a shared variable so it should be synchronized with a mutex (or made atomic)
* If a member variable is itself a mutex, it should be mutable. This is required to use it inside a const member function. * If a member variable is itself a mutex, it should be mutable. This is required to use it inside a const member function.
For more information see the following article from Herb Sutter: http://herbsutter.com/2013/05/24/gotw-6a-const-correctness-part-1-3/