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

Improved format

Browse Source
This commit is contained in:
rob100
2015-06-29 11:27:21 +02:00
parent 3663b977cd
commit 51821c8741
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
07-Considering_Threadability.md
View File

@@ -11,8 +11,6 @@ Global data leads to unintended side effects between functions and can make code
Much slower in threaded environments. In many or maybe even most cases, copying data is faster. Plus with move operations and such and things.
## Mutex and mutable go together (M&M rule, C++11)
For member variables it is good practice to use mutex and mutable together. This applies in both ways:
1) A mutable member variable is presumed to be a shared variable so it should be synchronized with a mutex (or made atomic)
2) If a member variable is itself a mutex, it should be mutable. This is required to use it inside a const member function.
* 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.