From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id A638817D9EDE for ; Sun, 21 Sep 2014 11:23:44 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (smtp.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 62DB3B5D8AB for ; Sun, 21 Sep 2014 11:04:53 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 9F13B97A832 for ; Sun, 21 Sep 2014 11:04:54 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GgQyBReDlWQi for ; Sun, 21 Sep 2014 11:04:54 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 7D46D97A826 for ; Sun, 21 Sep 2014 11:04:54 +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 2551195243E for ; Sun, 21 Sep 2014 11:04:32 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 1453F1204B1; Sun, 21 Sep 2014 11:04:26 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with ESMTPS id 1D14012046E for ; Sun, 21 Sep 2014 11:04:22 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=DRnTTVbvOJTPBMcpt7k8faXG22k=; b=wV19tiH5Hy0q895qKc cmuL4tdigawEFE4LPXnBOlpAKto6An5aZONzgiED1uzIxKf/0EaIxYaxgJ0eiSbp 2LWEn8jvQ4Rb8v3dQg+8GVX3QHiwRNxHIxmHTr7egGRLPJFhHmA53X14QPyTBH9x krSGHG1xk0gqFGyoTvG6Bu5Wk= Received: by mf184.sendgrid.net with SMTP id mf184.32117.541E322322 2014-09-21 02:04:20.074148063 +0000 UTC Received: from herokuapp.com (ec2-54-87-31-254.compute-1.amazonaws.com [54.87.31.254]) by ismtpd-025.iad1.sendgrid.net (SG) with ESMTP id 14895f3dc8e.66cb.616a25 for ; Sun, 21 Sep 2014 02:04:19 +0000 (GMT) Date: Sun, 21 Sep 2014 02:04:19 +0000 From: a7145@live.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 39429 X-Redmine-Project: common-ruby X-Redmine-Issue-Id: 10273 X-Redmine-Issue-Author: atlas X-Redmine-Sender: atlas X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: OOF Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4cuyYxykOUxT4Cc0dmSOndd5APqEdEksYkVe8qXVTmq0mE68QmRqZvXNPGTix710WANta1hxxKL8laeP0Q+Cjc5rOPxihIF+LWi4khl25VAFPPwxqNY39J6D5gQjyxy7E= X-ML-Name: ruby-core X-Mail-Count: 65179 Subject: [ruby-core:65179] [CommonRuby - Feature #10273] [Open] Immutable Ruby 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: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #10273 has been reported by Atlas Prime. ---------------------------------------- Feature #10273: Immutable Ruby https://bugs.ruby-lang.org/issues/10273 * Author: Atlas Prime * Status: Open * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- I watched Matz recent keynote about the future of Ruby. I wonder if Ruby can become an immutable language? That could be expedited by a port of Clojure's immutable types. Then add concurrency and distributed computing (perhaps modeled after Erlang). That surely would be a-ma-zing! Yet, I am not sure how well OOP can mix with this. But if it can be figured out, I think it would be worth it --more than anything else I can conceive of for a Ruby 3.0. Of course, this is also a HUGE change. -- https://bugs.ruby-lang.org/