From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ruby-core-bounces@ruby-lang.org>
X-Original-To: poffice@blade.nagaokaut.ac.jp
Delivered-To: poffice@blade.nagaokaut.ac.jp
Received: from kankan.nagaokaut.ac.jp (smtp.nagaokaut.ac.jp [133.44.2.24])
	by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 201FD1BA0009
	for <poffice@blade.nagaokaut.ac.jp>; Mon,  8 May 2017 11:59:18 +0900 (JST)
Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100])
	by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 0BC7AB5D85C
	for <poffice@blade.nagaokaut.ac.jp>; Mon,  8 May 2017 12:42:47 +0900 (JST)
Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75])
	by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 82B1818D1D87
	for <poffice@blade.nagaokaut.ac.jp>; Mon,  8 May 2017 12:42:47 +0900 (JST)
Received: from neon.ruby-lang.org (localhost [IPv6:::1])
	by neon.ruby-lang.org (Postfix) with ESMTP id 7F09F120643;
	Mon,  8 May 2017 12:42:46 +0900 (JST)
X-Original-To: ruby-core@ruby-lang.org
Delivered-To: ruby-core@ruby-lang.org
Received: from mail.atdot.net (ik1-326-23156.vs.sakura.ne.jp [153.126.180.160])
 by neon.ruby-lang.org (Postfix) with ESMTP id 1854312045C
 for <ruby-core@ruby-lang.org>; Mon,  8 May 2017 12:42:42 +0900 (JST)
To: Ruby developers <ruby-core@ruby-lang.org>
References: <20170402011414.AEA9B64CEE@svn.ruby-lang.org>
 <8a2b82e3-dc07-1945-55f9-5a474e89130b@ruby-lang.org>
 <20170402023514.GB30476@dcvr>
 <76459664-9857-4244-7d43-79b24e737efc@atdot.net>
 <20170403044254.GA16328@starla> <20170508003315.GA3789@starla>
 <38090d10-c6a1-5097-66af-130275d773ea@atdot.net>
 <2b47c736-08d8-095b-0454-2dd0b1020b03@atdot.net>
 <20170508030120.GB24763@starla>
From: SASADA Koichi <ko1@atdot.net>
Message-ID: <94ca8f9a-7001-12d3-323d-8c5751569c51@atdot.net>
Date: Mon, 8 May 2017 12:42:36 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170508030120.GB24763@starla>
X-ML-Name: ruby-core
X-Mail-Count: 81033
Subject: [ruby-core:81033] Re: [ruby-cvs:65407] normal:r58236 (trunk):
 thread.c: comments on M:N threading [ci skip]
X-BeenThere: ruby-core@ruby-lang.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ruby developers <ruby-core@ruby-lang.org>
List-Id: Ruby developers <ruby-core.ruby-lang.org>
List-Unsubscribe: <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>, 
 <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
List-Post: <mailto:ruby-core@ruby-lang.org>
List-Help: <mailto:ruby-core-request@ruby-lang.org?subject=help>
List-Subscribe: <http://lists.ruby-lang.org/cgi-bin/mailman/listinfo/ruby-core>, 
 <mailto:ruby-core-request@ruby-lang.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ruby-core-bounces@ruby-lang.org
Sender: "ruby-core" <ruby-core-bounces@ruby-lang.org>

On 2017/05/08 12:01, Eric Wong wrote:
>>> .
>> `Fiber.scheduler.add_auto_fiber{ ... }` (naming is not fixed) (operation
>> for scheduler) is my first idea.
> Too verbose, I think.  If I want to type more, I would not be
> using Ruby :)   How about adding kwarg to Fiber.new?

This design introduce new aspect: can we make schedulers per a thread?

-- 
// SASADA Koichi at atdot dot net