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 198031AA07F4 for ; Thu, 4 Aug 2016 15:14:51 +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 AEC8BB5D901 for ; Thu, 4 Aug 2016 15:48:26 +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 42E3518CC8CE for ; Thu, 4 Aug 2016 15:48:27 +0900 (JST) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 4A4B11204EE; Thu, 4 Aug 2016 15:48:26 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id E0FA31204E1 for ; Thu, 4 Aug 2016 15:48:22 +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=kBWhnW8ojwbQrkMPZk4Z5iRR+zs=; b=EStpyWXuYq1Cq9tRAu 7+DMvQM+Le6g3QuP/IttO74llOlvHdtX9oT1qV0lUEeA2lu7Eksw6cSXGNQv5NRn OdA4N5LkTmir9o88tsesZjfDA7nWaoD7zQQQdnkRQyH6DEsli0I+U2hJaxUkP2Co l1wcknNB9o4WTDV5YSeolsSfc= Received: by filter0606p1mdw1.sendgrid.net with SMTP id filter0606p1mdw1.30512.57A2E52C14 2016-08-04 06:48:12.385824694 +0000 UTC Received: from herokuapp.com (ec2-54-166-21-177.compute-1.amazonaws.com [54.166.21.177]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id lWbWLUSQQS2Ycce_cj32kw Thu, 04 Aug 2016 06:48:12.275 +0000 (UTC) Date: Thu, 04 Aug 2016 06:48:12 +0000 From: shyouhei@ruby-lang.org To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 51467 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11337 X-Redmine-Issue-Author: rosenfeld X-Redmine-Issue-Assignee: matz X-Redmine-Sender: shyouhei 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/Ymy4QrNMhiuLXJG8OTL2vJD1yS7FOL4R7yNT0C03y1exH9Herf3Ola2HUmmKvT nvqwXyWO4VAeq5v0MR+c95I418YePtHGzmFXKWz5LQcFVCyvYOdef0UnwnuiNHvg3jDjYtJwbabAC5 iJoZkN4gJTMYCZfAKMrN4aY6jE7vKK681L77lsyJ7I0kw/BKm/J3c5MPCw== X-ML-Name: ruby-core X-Mail-Count: 76701 Subject: [ruby-core:76701] [Ruby trunk Feature#11337][Closed] Allow rescue without begin inside blocks 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 #11337 has been updated by Shyouhei Urabe. Status changed from Open to Closed Hmm.. Thank you for the check. It is complicated than I thought. Closing this one anyway. ---------------------------------------- Feature #11337: Allow rescue without begin inside blocks https://bugs.ruby-lang.org/issues/11337#change-59919 * Author: Rodrigo Rosenfeld Rosas * Status: Closed * Priority: Normal * Assignee: Yukihiro Matsumoto ---------------------------------------- While it's possible to have rescue's without begin in method definitions it's not possible to have the same facility inside blocks. For example, this is currently not possible: ~~~ 1.times do abc rescue p 'error' end ~~~ But this is possible ~~~ def a abc rescue p 'error' end ~~~ Would it be possible to also allow rescue without begin inside blocks too? -- https://bugs.ruby-lang.org/