fix ractor's doc. [ci skip]

This commit is contained in:
Koichi Sasada 2020-12-22 01:05:52 +09:00
parent 520dcbd600
commit c34c6a89cb
Notes: git 2020-12-22 06:10:07 +09:00
2 changed files with 50 additions and 23 deletions

View File

@ -1935,16 +1935,25 @@ ractor_moved_missing(int argc, VALUE *argv, VALUE self)
* ClosedError is a descendant of StopIteration, so the closing of the ractor will break * ClosedError is a descendant of StopIteration, so the closing of the ractor will break
* the loops without propagating the error: * the loops without propagating the error:
* *
* r = Ractor.new { 3.times { puts "Received: " + receive } } * r = Ractor.new do
* loop do
* msg = receive # raises ClosedError and loop traps it
* puts "Received: #{msg}"
* end
* puts "loop exited"
* end
* *
* loop { r.send "test" } * 3.times{|i| r << i}
* r.close_incoming
* r.take
* puts "Continue successfully" * puts "Continue successfully"
* *
* This will print: * This will print:
* *
* Received: test * Received: 0
* Received: test * Received: 1
* Received: test * Received: 2
* loop exited
* Continue successfully * Continue successfully
*/ */
@ -2004,7 +2013,6 @@ ractor_moved_missing(int argc, VALUE *argv, VALUE self)
* *
*/ */
void void
Init_Ractor(void) Init_Ractor(void)
{ {

View File

@ -1,14 +1,19 @@
# Ractor is a Actor-model abstraction for Ruby that provides thread-safe parallel execution. # Ractor is a Actor-model abstraction for Ruby that provides thread-safe parallel execution.
# #
# To achieve this, ractors severely limit data sharing between different ractors. # Ractor.new can make new Ractor and it will run in parallel.
# Unlike threads, ractors can't access each other's data, nor any data through variables of
# the outer scope.
# #
# # The simplest ractor # # The simplest ractor
# r = Ractor.new {puts "I am in Ractor!"} # r = Ractor.new {puts "I am in Ractor!"}
# r.take # allow it to finish # r.take # wait it to finish
# # here "I am in Ractor!" would be printed # # here "I am in Ractor!" would be printed
# #
# Ractors do not share usual objects, so the some kind of thread-safety concerns such as data-race,
# race-conditions are not available on multi-ractor programming.
#
# To achieve this, ractors severely limit object sharing between different ractors.
# For example, unlike threads, ractors can't access each other's objects, nor any objects through
# variables of the outer scope.
#
# a = 1 # a = 1
# r = Ractor.new {puts "I am in Ractor! a=#{a}"} # r = Ractor.new {puts "I am in Ractor! a=#{a}"}
# # fails immediately with # # fails immediately with
@ -17,8 +22,8 @@
# On CRuby (the default implementation), Global Virtual Machine Lock (GVL) is held per ractor, so # On CRuby (the default implementation), Global Virtual Machine Lock (GVL) is held per ractor, so
# ractors are performed in parallel without locking each other. # ractors are performed in parallel without locking each other.
# #
# Instead of accessing the shared state, the data should be passed to and from ractors via # Instead of accessing the shared state, the objects should be passed to and from ractors via
# sending and receiving messages, thus making them _actors_ ("Ractor" stands for "Ruby Actor"). # sending and receiving objects as messages.
# #
# a = 1 # a = 1
# r = Ractor.new do # r = Ractor.new do
@ -71,14 +76,17 @@
# #
# It is said that Ractor receives messages via the <em>incoming port</em>, and sends them # It is said that Ractor receives messages via the <em>incoming port</em>, and sends them
# to the <em>outgoing port</em>. Either one can be disabled with Ractor#close_incoming and # to the <em>outgoing port</em>. Either one can be disabled with Ractor#close_incoming and
# Ractor#close_outgoing respectively. # Ractor#close_outgoing respectively. If a ractor terminated, its ports will be closed
# automatically.
# #
# == Shareable and unshareable objects # == Shareable and unshareable objects
# #
# When the object is sent to and from the ractor, it is important to understand whether the # When the object is sent to and from the ractor, it is important to understand whether the
# object is shareable or not. Shareable objects are basically those which can be used by several # object is shareable or unshareable. Most of objects are unshareable objects.
# threads without compromising thread-safety; e.g. immutable ones. Ractor.shareable? allows to #
# check this, and Ractor.make_shareable tries to make object shareable if it is not. # Shareable objects are basically those which can be used by several threads without compromising
# thread-safety; e.g. immutable ones. Ractor.shareable? allows to check this, and Ractor.make_shareable
# tries to make object shareable if it is not.
# #
# Ractor.shareable?(1) #=> true -- numbers and other immutable basic values are # Ractor.shareable?(1) #=> true -- numbers and other immutable basic values are
# Ractor.shareable?('foo') #=> false, unless the string is frozen due to # freeze_string_literals: true # Ractor.shareable?('foo') #=> false, unless the string is frozen due to # freeze_string_literals: true
@ -115,7 +123,7 @@
# the ractor, showing it is different objects. But the second array's element, which is a # the ractor, showing it is different objects. But the second array's element, which is a
# shareable frozen string, has the same object_id.) # shareable frozen string, has the same object_id.)
# #
# Deep cloning of the data may be slow, and sometimes impossible. Alternatively, # Deep cloning of the objects may be slow, and sometimes impossible. Alternatively,
# <tt>move: true</tt> may be used on sending. This will <em>move</em> the object to the # <tt>move: true</tt> may be used on sending. This will <em>move</em> the object to the
# receiving ractor, making it inaccessible for a sending ractor. # receiving ractor, making it inaccessible for a sending ractor.
# #
@ -138,8 +146,13 @@
# Notice that even +inspect+ (and more basic methods like <tt>__id__</tt>) is inaccessible # Notice that even +inspect+ (and more basic methods like <tt>__id__</tt>) is inaccessible
# on a moved object. # on a moved object.
# #
# Besides frozen objects, shareable objects are instances of Module, Class and Ractor itself. Modules # Besides frozen objects, there are shareable objects. Class and Module objects are shareable so
# and classes, though, can not access instance variables from ractors other than main: # the Class/Module definitons are shared between ractors. Ractor objects are also shareable objects.
# All operations for the shareable mutable objects are thread-safe, so the thread-safety property
# will be kept. We can not define mutable sharable objects in Ruby, but C extensions can introduce them.
#
# It is prohibited to access instance variables of mutable shareable objects (especially Modules and classes)
# from ractors other than main:
# #
# class C # class C
# class << self # class << self
@ -186,8 +199,8 @@
# #
# == Ractors vs threads # == Ractors vs threads
# #
# Each ractor creates its own thread. New threads can be created from inside ractor, having the full # Each ractor creates its own thread. New threads can be created from inside ractor
# access to its data (and, on CRuby, sharing GVL with other threads of this ractor). # (and, on CRuby, sharing GVL with other threads of this ractor).
# #
# r = Ractor.new do # r = Ractor.new do
# a = 1 # a = 1
@ -208,6 +221,10 @@
# It is **only for demonstration purposes** and shouldn't be used in a real code. # It is **only for demonstration purposes** and shouldn't be used in a real code.
# Most of the times, just #take is used to wait till ractor will finish. # Most of the times, just #take is used to wait till ractor will finish.
# #
# == Reference
#
# See {Ractor desgin doc}[rdoc-ref:doc/ractor.md] for more details.
#
class Ractor class Ractor
# Create a new Ractor with args and a block. # Create a new Ractor with args and a block.
# #
@ -258,8 +275,9 @@ class Ractor
# Returns total count of Ractors currently running. # Returns total count of Ractors currently running.
# #
# Ractor.count #=> 1 # Ractor.count #=> 1
# r = Ractor.new(name: 'example') {sleep(0.1)} # r = Ractor.new(name: 'example') { Ractor.yield(1) }
# Ractor.count #=> 2 (main + example ractor) # Ractor.count #=> 2 (main + example ractor)
# r.take # wait for Ractor.yield(1)
# r.take # wait till r will finish # r.take # wait till r will finish
# Ractor.count #=> 1 # Ractor.count #=> 1
def self.count def self.count
@ -374,7 +392,8 @@ class Ractor
# Still received only one # Still received only one
# Received: message2 # Received: message2
# #
# If close_incoming was called on the ractor, the method raises Ractor::ClosedError: # If close_incoming was called on the ractor, the method raises Ractor::ClosedError
# if there are no more messages in incoming queue:
# #
# Ractor.new do # Ractor.new do
# close_incoming # close_incoming