From: v.semovich@...
Date: 2021-02-13T23:04:02+00:00
Subject: [ruby-core:102479] [Ruby master Misc#11904] Why was	Thread.exclusive deprecated?

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


�������� ������������! 
 ���������� ���������������������������� �������������������� ���� �������� ����������:  http://anubi.ru : 
<a href=http://anubi.ru/humor/>�������� ����</a> �������������� �������� ���� �������� 
�������������������� Lens Culture Portrait Awards 2015 http://anubi.ru/foto-prikoly-interesnoe/3796-pobediteli-lens-culture-portrait-awards-2015.html 
������������������ �������������� �������������� 2020 <a href=http://anubi.ru/interesnoe/11621-poslednie-osennie-peyzazhi-2020.html> ������������������ �������������� �������������� 2020 </a> 
http://anubi.ru/foto-prikoly-interesnoe/1158-puteshestvie-po-kamchatke.html

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

* 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.




-- 
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>