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.0 required=3.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, FORGED_GMAIL_RCVD,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, 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 0379A1F453 for ; Wed, 30 Jan 2019 12:12:28 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id A511612189B; Wed, 30 Jan 2019 21:12:24 +0900 (JST) Received: from o1678916x28.outbound-mail.sendgrid.net (o1678916x28.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 68AC4121835 for ; Wed, 30 Jan 2019 21:12:22 +0900 (JST) Received: by filter0089p3mdw1.sendgrid.net with SMTP id filter0089p3mdw1-30142-5C5194A2-1F 2019-01-30 12:12:18.455402743 +0000 UTC m=+141142.147137635 Received: from herokuapp.com (ec2-54-164-89-245.compute-1.amazonaws.com [54.164.89.245]) by ismtpd0043p1mdw1.sendgrid.net (SG) with ESMTP id rDSji8hJSpy545oaLIW3Yw for ; Wed, 30 Jan 2019 12:12:18.331 +0000 (UTC) Date: Wed, 30 Jan 2019 12:12:19 +0000 (UTC) From: eregontp@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 66790 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15574 X-Redmine-Issue-Author: ko1 X-Redmine-Issue-Assignee: matz X-Redmine-Sender: Eregon 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS55e+abV9B78s+Z10MD13UdGFOryAsBkpkEJf gmxu2ezTD/Uvu3HMkn/G1V45hckw4z/YgOyMfPh12mi7NdSvfm1FI5IjkwbacSWOn/byJK+NMMV318 Xv715QgiSap1CSA5H5BEtKVuQusWAqy7AtsBLr/oGOf1ht6EP0hQBFgGXg== X-ML-Name: ruby-core X-Mail-Count: 91338 Subject: [ruby-core:91338] [Ruby trunk Feature#15574] Prohibit to pass a block on super() implicitly 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 #15574 has been updated by Eregon (Benoit Daloze). I would think this is tricky for compatibility (there is definitely code relying on it), but let's see. ---------------------------------------- Feature #15574: Prohibit to pass a block on super() implicitly https://bugs.ruby-lang.org/issues/15574#change-76587 * Author: ko1 (Koichi Sasada) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) * Target version: ---------------------------------------- As described in [Feature #15554], `super()` (not `super`) pass the given block. ``` class C def foo p block_given? end end class C1 < C def foo super #=> true super() #=> true end end C1.new.foo{} ``` `super` (without parameters) passes all passed parameters so it is no surprise to pass given block. However, `super()` (with parameters. In this case, it passes 0 parameters) also pass given block implicitly. I'm not sure who use this behavior, but I think it is simple to prohibit such implicit block passing. -- https://bugs.ruby-lang.org/