kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

Make the Ractor-safe section more fluent

Browse source
This commit is contained in:
Benoit Daloze 2022-01-10 13:08:59 +01:00
parent b4d0d07e2c
commit ca97001a94
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/extension.rdoc
View file

@ -2178,10 +2178,11 @@ because g_called global variable should be synchronized by other
ractor's threads. To avoid such data-race, some synchronization should ractor's threads. To avoid such data-race, some synchronization should
be used. Check include/ruby/thread_native.h and include/ruby/atomic.h. be used. Check include/ruby/thread_native.h and include/ruby/atomic.h.
On the Ractor mechanism, most of objects given by the method parameters With Ractors, all objects given as method parameters and the receiver (self)
or the receiver are isolated by Ractor's boundary, it is easy to make are guaranteed to be from the current Ractor or to be shareable. As a
thread-safe code than usual thread-programming in general. For example, consequence, it is easier to make code ractor-safe than to make code generally
we don't need to lock an array object to access the element of it. thread-safe. For example, we don't need to lock an array object to access the
element of it.
(3) Check the thread-safety of any used library (3) Check the thread-safety of any used library