From: "Eregon (Benoit Daloze) via ruby-core" <ruby-core@...>
Date: 2026-04-17T21:01:30+00:00
Subject: [ruby-core:125314] [Ruby Bug#22007] Inconsistent type checking on rescue

Issue #22007 has been updated by Eregon (Benoit Daloze).


I think a better fix, related to this issue, would be to stop checking the class of rescue clauses, I think any expression should be allowed and just call `===` on them.

So one could do e.g.:
```ruby
begin
  raise "nope"
rescue -> e { e.message.include? "o" }
  p :OK
end
```

----------------------------------------
Bug #22007: Inconsistent type checking on rescue
https://bugs.ruby-lang.org/issues/22007#change-117067

* Author: zenspider (Ryan Davis)
* Status: Open
* ruby -v: 4.0.2
* Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN
----------------------------------------
this works fine (but I don't think it should):
```ruby
begin
  raise "nope"
rescue RuntimeError, /why am I allowed?/, "or me?" => e
  # yay
end
```
whereas this version shows a type error, which seems right:
```ruby
begin
  begin
    raise "nope"
  rescue /why am I NOT allowed/, "if I was allowed before?" => e
    p e
  end
rescue TypeError => te
  p te
end
```
I think all the args on rescue should be checked to be `Module`



-- 
https://bugs.ruby-lang.org/
______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/