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-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY 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 C68441F55B for ; Wed, 13 May 2020 16:49:30 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 247B1120A77; Thu, 14 May 2020 01:42:25 +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 BD553120A76 for ; Thu, 14 May 2020 01:42:21 +0900 (JST) Received: by filter0135p3las1.sendgrid.net with SMTP id filter0135p3las1-28320-5EBC237D-A6 2020-05-13 16:42:37.445080669 +0000 UTC m=+2400012.736224892 Received: from herokuapp.com (unknown) by ismtpd0008p1iad2.sendgrid.net (SG) with ESMTP id 6ofaMWMoRXKJoYygRvGAcg for ; Wed, 13 May 2020 16:42:37.257 +0000 (UTC) Date: Wed, 13 May 2020 16:42:37 +0000 (UTC) From: james@nakagawa.ca Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 74084 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 16854 X-Redmine-Issue-Author: jamesnakagawa X-Redmine-Sender: jamesnakagawa 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?REQifTATFWqNSS4LR9tjuKRuxKXhH+fv=2FFWZj9yCnaJrNN4HRB4EpaIc9mBtmr?= =?us-ascii?Q?=2FhFcdqEe5gbOTsEgY1I74kNo8jjziDoxmI2P8o6?= =?us-ascii?Q?GafWTESsm+O06G5G54rYYFsQ4nXh+ZFTuPFh1wq?= =?us-ascii?Q?k1nAdTb7O8THyQ8+oQrm5FqlDPXflBWRrC+dQ+c?= =?us-ascii?Q?PaZksvuI2OBrDyWQFLiIs0mUOywu2licbYQ=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 98323 Subject: [ruby-core:98323] [Ruby master Bug#16854] Using (...) when the method name is a keyword generates error 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 #16854 has been reported by jamesnakagawa (James Nakagawa). ---------------------------------------- Bug #16854: Using (...) when the method name is a keyword generates error https://bugs.ruby-lang.org/issues/16854 * Author: jamesnakagawa (James Nakagawa) * Status: Open * Priority: Normal * ruby -v: 2.7.0 * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- Although I wouldn't generally recommend it, naming a method `true` is allowed. However, in combination with the new argument forwarding keyword `...`, a syntax error is generated which does not occur with other argument choices. This came up for me on my Rails project where an enumerated database column was defined to allow the values `:true`, `:false` (not an unreasonable request in itself). Active Record's generated class tried to contain methods by these names. Try this code for yourself: ```ruby class Works def true(*args) puts(*args) end end Works.new.true 1, 2, 3 # => 1, 2, 3 class WontWork def true(...) puts(...) end end # => freezes ``` -- https://bugs.ruby-lang.org/