Issue #10042 has been updated by Recursive Madman. I see how it would conflict when both forms (`do_a rescue(TypeError)` and `do_a rescue(TypeError) do_b`) are supported (the parser can't decide between recognizing parenthesized exceptions or stmt), but when the former form (i.e. not specifying an exception) is no longer allowed, `do_a rescue(TypeError)` becomes invalid code. ---------------------------------------- Feature #10042: Deprecate postfix rescue syntax for removal in 3.0 https://bugs.ruby-lang.org/issues/10042#change-49910 * Author: Charles Nutter * Status: Open * Priority: Normal * Assignee: Yukihiro Matsumoto * Category: core * Target version: Next Major ---------------------------------------- The postfix rescue notation is convenient...but almost always is a really bad antipattern. An example of the notation: Integer(f) rescue f # returns f if it is not parseable as an Integer It silently ignores all StandardError raised by a piece of code...which often covers *many* more exceptions than the user *wants* to be ignoring. It also hides the cost of constructing and throwing away all those ignored exceptions. I believe Matz has even said in the past that he regrets adding the feature. In any case, I propose that "rescue nil" should be deprecated with a warning (either always on or only when verbose) and we should plan to remove it in 3.0. Who's with me?! -- https://bugs.ruby-lang.org/