std::defer_lock_t, std::try_to_lock_t, std::adopt_lock_t
Aus cppreference.com
 | This page has been machine-translated from the English version of the wiki using Google Translate. The translation may contain errors and awkward wording. Hover over text to see the original version. You can help to fix errors and improve the translation. For instructions click here. |
struct defer_lock_t {}; | (seit C++11) | |
struct try_to_lock_t {}; | (seit C++11) | |
struct adopt_lock_t {}; | (seit C++11) | |
std::defer_lock_t, std::try_to_lock_t und std::adopt_lock_t sind leer struct Tag-Typen verwendet werden, um den Verschluss Strategie für std::lock_guard und std::unique_lock .Original:
std::defer_lock_t, std::try_to_lock_t and std::adopt_lock_t are empty struct tag types used to specify locking strategy for std::lock_guard and std::unique_lock.The text has been machine-translated via Google Translate.
You can help to correct and verify the translation. Click here for instructions.
You can help to correct and verify the translation. Click here for instructions.
Type Original: Type The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. | Effect(s) |
defer_lock_t | nicht erwerben Besitz des Mutex Original: do not acquire ownership of the mutex The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. |
try_to_lock_t | versuchen Besitz des Mutex ohne Blockierung zu erwerben Original: try to acquire ownership of the mutex without blocking The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. |
adopt_lock_t | nehmen den aufrufenden Thread hat bereits Besitz des Mutex Original: assume the calling thread already has ownership of the mutex The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. |
[Bearbeiten]Beispiel
#include <mutex>#include <thread> struct bank_account {explicit bank_account(int balance): balance(balance){}int balance;std::mutex m;}; void transfer(bank_account &from, bank_account &to, int amount){// attempt to lock both mutexes without deadlockstd::lock(from.m, to.m); // make sure both already-locked mutexes are unlocked when // we're done; if we just used the lock_guard without std::lock// and std::adopt_lock, we might deadlock with other calls to transferstd::lock_guard lock1(from.m, std::adopt_lock);std::lock_guard lock2(to.m, std::adopt_lock); from.balance-= amount; to.balance+= amount;} int main(){ bank_account my_account(100); bank_account your_account(50); std::thread t1(transfer, my_account, your_account, 10);std::thread t2(transfer, your_account, my_account, 5); t1.join(); t2.join();}
[Bearbeiten]Siehe auch
tag Konstanten verwendet werden, um Sperrstrategie angeben Original: tag constants used to specify locking strategy The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. (konstanten) | |
konstruiert eine lock_guard, gegebenenfalls Verriegeln des gegebenen Mutex Original: constructs a lock_guard, optionally locking the given mutex The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. (öffentliche Elementfunktion of std::lock_guard) | |
konstruiert eine unique_lock, wahlweise Verriegelung der mitgelieferten Mutex Original: constructs a unique_lock, optionally locking the supplied mutex The text has been machine-translated via Google Translate. You can help to correct and verify the translation. Click here for instructions. (öffentliche Elementfunktion of std::unique_lock) | |
