std::defer_lock_t, std::try_to_lock_t, std::adopt_lock_t
De 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 { }; |
(ya que C + +11) | |
| struct try_to_lock_t { }; |
(ya que C + +11) | |
| struct adopt_lock_t { }; |
(ya que C + +11) | |
std::defer_lock_t, std::try_to_lock_t y std::adopt_lock_t están vacías tipos de variables struct usan para especificar bloqueo estrategia para std::lock_guard y 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.
| Tipo
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
|
no adquieren la propiedad de la exclusión mutua
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
|
tratar de adquirir la propiedad del mutex sin bloquear
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
|
asumir el subproceso de la llamada tiene ya la propiedad de la exclusión mutua
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. |
[editar] Ejemplo
#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 deadlock std::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 transfer std::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(); }
[editar] Ver también
| constantes de etiqueta se utiliza para especificar la estrategia de bloqueo 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. (constante) | |
| construye una lock_guard, opcionalmente bloquear el mutex dado 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. (miembro público of std::lock_guard función)
| |
| construye una unique_lock, opcionalmente bloquear el mutex suministrado 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. (miembro público of std::unique_lock función)
| |