[ruby-core:101947] [Ruby master Misc#11904] Why was Thread.exclusive deprecated?

Issue #11904 has been updated by Robertjoise (Robertjoise Robertjoise).

File 476.gif added

Высокодоходные инвестиции теперь доступны и в Подольске! 
 
 
Ваш доход до 25% в месяц. Вы сами решаете, во что инвестировать. Все в одном кабинете. 
Вы можете находится в Владимире, Северске или любом другом городе или даже стране. 
 
Управлять инвестициями можно из своего кабинета.

----------------------------------------
Misc #11904: Why was Thread.exclusive deprecated?
https://bugs.ruby-lang.org/issues/11904#change-89798

* 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:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>