From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,SPF_PASS, T_DKIM_INVALID shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id B2AA21FADE for ; Tue, 12 Sep 2017 13:56:17 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 760111208E0; Tue, 12 Sep 2017 22:56:16 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 9906B1208DF for ; Tue, 12 Sep 2017 22:56:14 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=7/unAC6XXZpKqYyzqrGSZLQiCLY=; b=N4GGZbiWtlzaUZDdVy Y1aD8g03ZmUEkVbRA5IdhAo4/X1QPOynMUiIZjONWB1AaOkYpIaPchUD4JFEWYyZ QsfN3mTMCJ1miuvGdhP/olA6xveYd64uAFMuWNyqx8vC/42B0jzAobIKcSuqUgIj mT0wtar5SeRKzkKE3N+xDBJVk= Received: by filter0015p3mdw1.sendgrid.net with SMTP id filter0015p3mdw1-7590-59B7E77B-36 2017-09-12 13:56:11.797411849 +0000 UTC Received: from herokuapp.com (ec2-54-234-68-254.compute-1.amazonaws.com [54.234.68.254]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id JAHxhbs9Q9qeo4h5SigpKQ Tue, 12 Sep 2017 13:56:11.691 +0000 (UTC) Date: Tue, 12 Sep 2017 13:56:12 +0000 (UTC) From: git@chuckremes.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 57845 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 13821 X-Redmine-Issue-Author: cremes X-Redmine-Sender: cremes X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS6jzeiLuCFFC/S4J/vEuytk8IaunXie7zHcyU DOH+1S+hw8/Q6SOCnnBwDcy3iToBB2GWSP770ptp17LsQstca+M8BXwWT31JP3pSIg92A0sTHIdz6i OVvy9ZHnABk61g+Z5iwei80Nl8Jd0Ux7KTsiwSnL0hWj8js3s8cv9PHDdg== X-ML-Name: ruby-core X-Mail-Count: 82763 Subject: [ruby-core:82763] [Ruby trunk Feature#13821] Allow fibers to be resumed across threads X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #13821 has been updated by cremes (Chuck Remes). Added ticket 13893 (https://bugs.ruby-lang.org/issues/13893) to track a feature request to cleanup fiber-local and thread-local handling in the Fiber and Thread classes. ---------------------------------------- Feature #13821: Allow fibers to be resumed across threads https://bugs.ruby-lang.org/issues/13821#change-66618 * Author: cremes (Chuck Remes) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- Given a Fiber created in ThreadA, Ruby 2.4.1 (and earlier releases) raise a FiberError if the fiber is resumed in ThreadB or any other thread other than the one that created the original Fiber. Sample code attached to demonstrate problem. If Fibers are truly encapsulating all of the data for the continuation, we should be allowed to move them between Threads and resume their operation. Why? One use-case is to support the async-await asynchronous programming model. In that model, a method marked async runs *synchronously* until the #await method is encountered. At that point the method is suspended and control is returned to the caller. When the #await method completes (asynchronously) then it may resume the suspended method and continue. The only way to capture this program state, suspend and resume, is via a Fiber. example: ``` class Wait include AsyncAwait def dofirst async do puts 'Synchronously print dofirst.' result = await { dosecond } puts 'dosecond is complete' result end end def dosecond async do puts 'Synchronously print dosecond from async task.' slept = await { sleep 3 } puts 'Sleep complete' slept end end def run task = dofirst puts 'Received task' p AsyncAwait::Task.await(task) end end Wait.new.run ``` ``` # Expected output: # Synchronous print dofirst. # Received task # Synchronously print dosecond from async task. # Sleep complete # dosecond is complete # 3 ``` Right now the best way to accomplish suspension of the #dofirst and #dosecond commands and allow them to run asynchronously is by passing those blocks to *another thread* (other than the callers thread) so they can be encapsulated in a new Fiber and then yielded. When it's time to resume after #await completes, that other thread must lookup the fiber and resume it. This is lots of extra code and logic to make sure that fibers are only resumed on the threads that created them. Allowing Fibers to migrate between threads would eliminate this problem. ---Files-------------------------------- fiber_across_threads.rb (377 Bytes) wait.rb (728 Bytes) -- https://bugs.ruby-lang.org/