From: nobu@... Date: 2017-08-31T02:07:43+00:00 Subject: [ruby-core:82541] [Ruby trunk Feature#13844] Toplevel returns should fire ensures Issue #13844 has been updated by nobu (Nobuyoshi Nakada). Tracker changed from Bug to Feature ruby -v deleted (ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16]) Backport deleted (2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN) The behavior was intentional. ---------------------------------------- Feature #13844: Toplevel returns should fire ensures https://bugs.ruby-lang.org/issues/13844#change-66349 * Author: headius (Charles Nutter) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- In the following contexts, a return always fires the ensure that wraps it: ``` [] ~/projects/ruby $ ruby -e 'def foo; return; ensure; p :x; end; foo' :x [] ~/projects/ruby $ ruby -e 'def foo; 1.times { begin; return; ensure; p :x; end }; end; foo' :x ``` However the new 2.4 support for toplevel returns does *not* fire ensures: ``` $ ruby -e 'begin; return; ensure; p :x; end' ``` I believe this is inconsistent with how returns work everywhere else (both valid and invalid returns always fire ensure) and it should be changed to match. -- https://bugs.ruby-lang.org/ Unsubscribe: