[ruby-core:101993] [Ruby master Misc#11904] Why was Thread.exclusive deprecated?
From:
marydean1295@...
Date:
2021-01-09 17:04:56 UTC
List:
ruby-core #101993
Issue #11904 has been updated by TylerSpouh (TylerSpouh TylerSpouh). Looking for an insatiable guy My private fotos <a href=http://tit18.com/?mary25>http://tit18.com/?mary25</a> My email: marydean1295@gmail.com ---------------------------------------- Misc #11904: Why was Thread.exclusive deprecated? https://bugs.ruby-lang.org/issues/11904#change-89842 * Author: bascule (Tony Arcieri) * Status: Rejected * Priority: Normal ---------------------------------------- initialize a mutex because the mutex must be initialized in a thread-safe context where it's not possible for multiple caller threads to initialize the mutex concurrently. One use case is here: this is an idempotent native function invoked via FFI. The contract is that it can be called repeatedly, but only by one thread at a time (concurrent calls from multiple threads can potentially corrupt its internal state): https://github.com/cryptosphere/rbnacl/blob/master/lib/rbnacl.rb#L88 Thread.exclusive is useful because it provides an implicit mutex you can ensure is initialized correctly before any other threads start. ---Files-------------------------------- 476.gif (1.97 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>