[ruby-core:115517] [Ruby master Bug#20026] Ruby doesn't throw a syntax error when rescuing with ||

[ruby-core:115517] [Ruby master Bug#20026] Ruby doesn't throw a syntax error when rescuing with ||

[arian (Arian Faurtosh) via ruby-core]

Issue #20026 has been reported by arian (Arian Faurtosh).

----------------------------------------
Bug #20026: Ruby doesn't throw a syntax error when rescuing with ||
https://bugs.ruby-lang.org/issues/20026

* Author: arian (Arian Faurtosh)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin23]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
We had a coworker new to ruby try an interesting syntax for rescue that doesn't result in a syntax error, and works partially.

Why does ruby allow the logical OR || operator, is there a purpose for this? If not this feels like it should be a syntax error, instead of resulting in partially working code.

``` ruby
class FooError < StandardError; end
class BarError < StandardError; end

# works
begin
  raise FooError
rescue FooError || BarError => e
  puts "rescued #{e.class}"
end

# doesn't work
begin
  raise FooError
rescue FooError || BarError => e
  puts "rescued #{e.class}"
end
```




-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/

[ruby-core:115518] [Ruby master Bug#20026] Ruby doesn't throw a syntax error when rescuing with ||

[arian (Arian Faurtosh) via ruby-core]

Issue #20026 has been updated by arian (Arian Faurtosh).


Actually I see what's going on here, this can be closed, not actually a ruby issue.

`FooError || BarError` is evaluating to `FooError`

----------------------------------------
Bug #20026: Ruby doesn't throw a syntax error when rescuing with ||
https://bugs.ruby-lang.org/issues/20026#change-105446

* Author: arian (Arian Faurtosh)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin23]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
We had a coworker new to ruby try an interesting syntax for rescue that doesn't result in a syntax error, and works partially.

Why does ruby allow the logical OR || operator, is there a purpose for this? If not this feels like it should be a syntax error, instead of resulting in partially working code.

``` ruby
class FooError < StandardError; end
class BarError < StandardError; end

# works
begin
  raise FooError
rescue FooError || BarError => e
  puts "rescued #{e.class}"
end

# doesn't work
begin
  raise FooError
rescue FooError || BarError => e
  puts "rescued #{e.class}"
end
```




-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/

[ruby-core:115530] [Ruby master Bug#20026] Ruby doesn't throw a syntax error when rescuing with ||

[nobu (Nobuyoshi Nakada) via ruby-core]

Issue #20026 has been updated by nobu (Nobuyoshi Nakada).


You may want to write:

```ruby
begin
  raise FooError
rescue FooError, BarError => e
  puts "rescued #{e.class}"
end
```

----------------------------------------
Bug #20026: Ruby doesn't throw a syntax error when rescuing with ||
https://bugs.ruby-lang.org/issues/20026#change-105462

* Author: arian (Arian Faurtosh)
* Status: Rejected
* Priority: Normal
* ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin23]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
We had a coworker new to ruby try an interesting syntax for rescue that doesn't result in a syntax error, and works partially.

Why does ruby allow the logical OR || operator, is there a purpose for this? If not this feels like it should be a syntax error, instead of resulting in partially working code.

``` ruby
class FooError < StandardError; end
class BarError < StandardError; end

# works
begin
  raise FooError
rescue FooError || BarError => e
  puts "rescued #{e.class}"
end

# doesn't work
begin
  raise FooError
rescue FooError || BarError => e
  puts "rescued #{e.class}"
end
```




-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/