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 B1AD117DC014 for ; Tue, 17 Nov 2015 11:36:28 +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 63764B5D896 for ; Tue, 17 Nov 2015 12:06:56 +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 8DA4018CC7B8 for ; Tue, 17 Nov 2015 12:06:56 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 6667D120443; Tue, 17 Nov 2015 12:06:55 +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 746A1120439 for ; Tue, 17 Nov 2015 12:06:36 +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=QMnr8Ce4PKQa3Lf4k1SOP/VsSoE=; b=Fgqk1gsIwIS2j1TPex 1JVP9spRcaYZJ/Awv4bolento9sFjdnVKpv+lDIophjJSKeJLul/RayJeoOvOz03 j0xhoDcRX7pkfbkQx4TO5udnUhat/+4hk+U21UtNRDrLU++YberRvNioh4DeP0ab B9JRyNosBiYVQD3/D5qJjXdtI= Received: by filter0430p1mdw1.sendgrid.net with SMTP id filter0430p1mdw1.16166.564A99B851 2015-11-17 03:06:32.860575941 +0000 UTC Received: from herokuapp.com (ec2-54-198-28-204.compute-1.amazonaws.com [54.198.28.204]) by ismtpd0002p1iad1.sendgrid.net (SG) with ESMTP id mAZ6InvlQTe-2Cy5-z9d5g for ; Tue, 17 Nov 2015 03:06:32.924 +0000 (UTC) Date: Tue, 17 Nov 2015 03:06:32 +0000 From: nobu@ruby-lang.org 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: 46167 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11690 X-Redmine-Issue-Author: danielpclark X-Redmine-Sender: nobu 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS4GdrOiRxff+hCa48C8ORLMYNMSw2NOqWbneB nRJqvClbWhfSKtw/HsRvZ7vGt7ApIPoAeqjcWao8aZml6Uq2GmuEc/ie1SYhq234uxCQdLoIT9oEGr UFofMhZuyh71dHvQ+CGQtggPJar8ywD1tgjk X-ML-Name: ruby-core X-Mail-Count: 71514 Subject: [ruby-core:71514] [Ruby trunk - Feature #11690] Update Hash during multiple assignment 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 #11690 has been updated by Nobuyoshi Nakada. Daniel P. Clark wrote: > Maybe we could replace `to_be_assigned_with` to `slurp`, `consume`, `devour`, or `injest` ;-) My dictionary doesn't have the last word, maybe a compound word from `inject` and `ingest`? ---------------------------------------- Feature #11690: Update Hash during multiple assignment https://bugs.ruby-lang.org/issues/11690#change-54886 * Author: Daniel P. Clark * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Given that we can assign multiple variables at once ~~~ruby a,b,c = 1,2,3 ~~~ It would be nice to be able to update a Hash during multiple assignment rather than replacing it. Currently ~~~ruby x = {a: 1, b: 2} x, y ,z = {c: 3}, 6, 7 x # => {c: 3} ~~~ What I propose is adding `Hash#update=` to permit updating during multiple assignment. ~~~ruby class Hash def update=(h) update(h) end end x = {a: 1, b: 2} x.update, y ,z = {c: 3}, 6, 7 x # => {a: 1, b: 2, c: 3} ~~~ This would be most useful in scenarios where a method or proc return multiple values. When the method returns the values we don't normally know the key outside where the hash assignment is. ~~~ruby example = proc { [{:hi => :hello}, 5] } hash = {} # Currently in Ruby with an Unknown key multiple assignment isn't an option hash[????], current = example.call # We currently have to two step it result, current = example.call hash.update(result) ~~~ But with `Hash#update=` we don't have to know the key. -- https://bugs.ruby-lang.org/