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 773241F453 for ; Wed, 30 Jan 2019 10:12:13 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id AFD89121262; Wed, 30 Jan 2019 19:12:10 +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 7CB07120FFE for ; Wed, 30 Jan 2019 19:12:08 +0900 (JST) Received: by filter0091p3mdw1.sendgrid.net with SMTP id filter0091p3mdw1-2840-5C517875-22 2019-01-30 10:12:05.463743897 +0000 UTC m=+134555.432832583 Received: from herokuapp.com (ec2-54-164-89-245.compute-1.amazonaws.com [54.164.89.245]) by ismtpd0010p1iad1.sendgrid.net (SG) with ESMTP id bSmJDGhwQMasPY7t3shHqA for ; Wed, 30 Jan 2019 10:12:05.378 +0000 (UTC) Date: Wed, 30 Jan 2019 10:12:07 +0000 (UTC) From: Webhostingonedollar102@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 66787 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15574 X-Redmine-Issue-Author: ko1 X-Redmine-Issue-Assignee: matz X-Redmine-Sender: bican304 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS5bZ/s8sb13z9TRmJX3Mhn/Ml7AW4Uxh+qxUk rLG9lSkmvSE6yV0Vq8HT44301zX51oKyOdnp4JKTcLCilNA75Zno6UQ10g/IUX/KQTQRCC+E0Fqah9 BUnkzJu4PamHZ0B0xtezEhya8wzktEp9lrnjKPQr9BAzbjkURuP1FIvw0w== X-ML-Name: ruby-core X-Mail-Count: 91335 Subject: [ruby-core:91335] [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 bican304 (josef bican). I extremely like your article. I had numerous helpful things from this article. I truly value your endeavors "99 rs domain godaddy":https://www.webhostingonedollar.com/godaddy-rs-99-web-hosting-domain.html for compose this post. A debt of gratitude is in order for offering that enlightening post to us. ---------------------------------------- Feature #15574: Prohibit to pass a block on super() implicitly https://bugs.ruby-lang.org/issues/15574#change-76584 * 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/