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

relax Fiber#transfer's restriction

Using Fiber#transfer with Fiber#resume for a same Fiber is
limited (once Fiber#transfer is called for a fiber, the fiber
can not be resumed more). This restriction was introduced to
protect the resume/yield chain, but we realized that it is too much
to protect the chain. Instead of the current restriction, we
introduce some other protections.

(1) can not transfer to the resuming fiber.
(2) can not transfer to the yielding fiber.
(3) can not resume transferred fiber.
(4) can not yield from not-resumed fiber.

[Bug #17221]

Also at the end of a transferred fiber, it had continued on root fiber.
However, if the root fiber resumed a fiber (and that fiber can resumed
another fiber), this behavior also breaks the resume/yield chain.
So at the end of a transferred fiber, switch to the edge of resume
chain from root fiber.
For example, root fiber resumed f1 and f1 resumed f2, transferred to
f3 and f3 terminated, then continue from the fiber f2 (it was continued
from root fiber without this patch).
This commit is contained in:
Koichi Sasada 2020-10-08 01:15:32 +09:00
parent 2fd71112fb
commit bf3b2a4374
Notes: git 2020-10-12 22:59:06 +09:00
7 changed files with 269 additions and 91 deletions

View file

@ -42,10 +42,22 @@ describe "Fiber.current" do
fiber3 = Fiber.new do
states << :fiber3
fiber2.transfer
flunk
ruby_version_is '3.0' do
states << :fiber3_terminated
end
ruby_version_is '' ... '3.0' do
flunk
end
end
fiber3.resume
states.should == [:fiber3, :fiber2, :fiber]
ruby_version_is "" ... "3.0" do
states.should == [:fiber3, :fiber2, :fiber]
end
ruby_version_is "3.0" do
states.should == [:fiber3, :fiber2, :fiber, :fiber3_terminated]
end
end
end