Bug #19779: `eval "return"` at top level raises `LocalJumpError`

• Status: Open
• Priority: Normal
• Assignee: -
• Target version: -
• ruby -v: 3.2.1
• Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN

[andrykonchin (Andrew Konchin)]

Wondering whether it's intentional behaviour. It seems it's the only difference I've noticed between calling return with and without eval:

ruby -e 'return'
ruby -e 'eval "return"'
(eval):1:in `<main>': unexpected return (LocalJumpError)
	from -e:1:in `eval'
	from -e:1:in `<main>'

[andrykonchin (Andrew Konchin)]

• ruby -v set to 3.2.1

[matz (Yukihiro Matsumoto)]

Since we allow top-level return (from 2.4), it is nice to allow this too. But to be frank, it is low priority.

Matz.

[jeremyevans0 (Jeremy Evans)]

I submitted a pull request to fix this: https://github.com/ruby/ruby/pull/8766