From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id B19241F463 for ; Tue, 24 Sep 2019 21:38:13 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 3C8B0120A04; Wed, 25 Sep 2019 06:38:04 +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 39CF11209B7 for ; Wed, 25 Sep 2019 06:38:01 +0900 (JST) Received: by filter0191p3mdw1.sendgrid.net with SMTP id filter0191p3mdw1-16881-5D8A8CBA-51 2019-09-24 21:38:02.721237644 +0000 UTC m=+88677.221432183 Received: from herokuapp.com (unknown [54.157.43.252]) by ismtpd0038p1iad2.sendgrid.net (SG) with ESMTP id 1g2mUhSxRlq9x3VEkym3aA for ; Tue, 24 Sep 2019 21:38:02.670 +0000 (UTC) Date: Tue, 24 Sep 2019 21:38:02 +0000 (UTC) From: daniel@dan42.com Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 70621 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 16178 X-Redmine-Issue-Author: Eregon X-Redmine-Issue-Assignee: matz X-Redmine-Sender: Dan0042 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: =?us-ascii?Q?8sy4RigFvRTdBfCVJrT9zb2J88PC92TMQwdNgaWYaq6dE37dUsFtDVSyiSMS5F?= =?us-ascii?Q?j2kXMOh7HZlyOE2FMPKQ380cTL1cj5k+2mk6RNm?= =?us-ascii?Q?jUny8VuiMWQPmfF=2FPi8jhUPFoXM1gi4FaReDiX8?= =?us-ascii?Q?bT51zv5Q7NYktl7NjwpWSY=2Ftl93IgA+2kEqS2DC?= =?us-ascii?Q?TM+wiEQfBy=2FVX18FMYNiXtEPtPv2k7UQr1A=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 95066 Subject: [ruby-core:95066] [Ruby master Bug#16178] Numbered parameters: _1 should be the same as |x| and _0 should not exist 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 #16178 has been updated by Dan0042 (Daniel DeLorme). `proc{ |x,| }.arity` == 1, so `_1` is consistent with that. In order to get the tuples' first value you would need to do `array_of_arrays.map{_2;_1}` because otherwise `_1` would mean the entire tuple. This argument is really weird. Is it really so unsufferable to use `_0` instead of `_1`? Do you really think it would be *better* if the meaning of `_1` changed depending on whether `_2` is also used? Sorry, but I can't wrap my head around that one. The current syntax is clean and straightforward: use `_0` in general and use `_1`,`_2`,etc for dereferencing. Maybe `_` or `__` would have been better than `_0`, but that's what we've got. > Try to convince me otherwise. > If not, in one week I want to apply this change. Please don't ask people to convince you when it's obvious you've already made up your mind. ---------------------------------------- Bug #16178: Numbered parameters: _1 should be the same as |x| and _0 should not exist https://bugs.ruby-lang.org/issues/16178#change-81699 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: * ruby -v: ruby 2.7.0dev (2019-09-24T12:57:54Z master 0e84eecc17) [x86_64-linux] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- Currently on trunk: ```ruby array = ["string", 42, [1, 2]] array.map { |x| x * 2 } # => ["stringstring", 84, [1, 2, 1, 2]] array.map { _1 * 2 } # => ["stringstring", 84, 2] ``` Oops, this trivial code just lost data and completely ignored the element class! This is clearly contrary to intuition and is very dangerous. Using `_0` instead has the correct behavior but it's clear we use 1-based indexing for numbered parameters, and it doesn't solve that `_1` has dangerous behavior. Basically the current behavior is that `_0` is the same as `|x|` and `_1` is the same as `|x,|`. `|x,|` is almost never used in Ruby, and for good reasons, it just throws away data/information/the class of the object. Such a dangerous operation should only be done when it's explicit, and the trailing comma in `|x,|` shows that, but `_1` does not. So let's make `_1` be `|x|` and remove `_0`. I am going to be harsh, but this discussion has gone too long without any serious written argument for the current behavior: I believe it's irrational and irresponsible to have `_1` be `|x,|`, it's just going to lead to nasty bugs. Try to convince me otherwise. If not, in one week I want to apply this change. >From the discussion in https://bugs.ruby-lang.org/issues/15723#note-127 and in https://bugs.ruby-lang.org/issues/15708 Some reactions to this behavior in https://twitter.com/eregontp/status/1115318993299083265 -- https://bugs.ruby-lang.org/