Issue #6739 has been updated by Boris Stitnicky.


How about introducing shorter "resc" keyword for error-specific inline rescue?

    do_messy_job resc TypeError: 42, NameError: 43

Tbh, inline rescue always leaves me with a feeling that I'm doing somethingunderhanded. Keyword "resc" would save precious 2 characters, while still being highly unique, so it could be argued that its introduction would not be too big deal. This omnivorous inline rescue has been really pissing me off for a long time.



----------------------------------------
Feature #6739: One-line rescue statement should support specifying an exception class
https://bugs.ruby-lang.org/issues/6739#change-48068

* Author: Marvin Glker
* Status: Feedback
* Priority: Normal
* Assignee: Yukihiro Matsumoto
* Category: core
* Target version: Next Major
----------------------------------------
=begin
Hi there,

When wrapping up a single line inside a (({begin}))/(({rescue})) block I feel constantly annoyed that I have to create a whole lot of bloated code just to rescue from a specific exception. For example:

  begin
    File.read("myfile.txt")
  rescue Errno::ENOENT
    puts "No file there"
  end

Now it's possible to do this:

  File.read("myfile.txt") rescue puts "No file there"

But this forces me to rescue from ((|StandardError|)) which is not really what I want, because it swallows exceptions I'd rather have wanted to see, e.g. if I mistyped `(({File.read}))' as `(({File.raed}))' this would be swallowed as well. I know it is possible to compress the multiline statements above into a single line by using semicolons, but it's better to avoid them as they decrease readability.

So my suggestion is to add something like the following syntax to Ruby:

  File.read("myfile.txt") rescue Errno::ENOENT, puts "No file there"

This way it is more concise than having to write five lines (instead of just one) and still reads good (as opposed to the semicolon trick). Maybe the syntax isn't ideal as the comma operator is already used elsewhere, but thegeneral idea should be clear though.

Valete,
Marvin
=end



-- 
https://bugs.ruby-lang.org/