From: recursive.madman@...
Date: 2014-11-11T14:43:29+00:00
Subject: [ruby-core:66206] [ruby-trunk - Feature #10042] Deprecate postfix rescue syntax for removal in 3.0

Issue #10042 has been updated by Recursive Madman.


An alternative syntax that doesn't introduce a new reserved word would be:
~~~
do_something_messy rescue(TypeError, NameError) do_something_with($!)
~~~

The syntax within the parentheses could be the same as after a block rescue, e.g.:
~~~
do_a rescue(SomeError => e) do_b(e)
~~~

This doesn't introduce a new reserved word and causes a syntax error on older ruby versions (thus preventing existing code from suddenly working differently).


----------------------------------------
Feature #10042: Deprecate postfix rescue syntax for removal in 3.0
https://bugs.ruby-lang.org/issues/10042#change-49902

* 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/