Issue #17512 has been reported by HParker (Adam Hess).

----------------------------------------
Bug #17512: ostruct super regression
https://bugs.ruby-lang.org/issues/17512

* Author: HParker (Adam Hess)
* Status: Open
* Priority: Normal
* ruby -v: 3.0.0
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
In ruby 3.0, Calling super on ostruct always returns nil. This is a regression in ruby 3.0 introduced when fixing another issue.

introduced by: 
- https://bugs.ruby-lang.org/issues/12136
- https://github.com/ruby/ruby/commit/e026e186f4a01aa3f6cd02ae6ef33f44f129361c

This unintentionally changed `super` behavior in classes that inherit from OpenStruct.

```ruby
require 'ostruct'

class Foo < OpenStruct
  def foo
    super
  end
end

p Foo.new(foo: 123).foo
```

```
Ruby 3.0:
=> nil
Ruby 2.7:
=> 123
```

Potential fix is to bring back some of the behavior reverted in issue #12136 to allow method missing to sometimes respond to methods with zero arguments.

This is implemented in: https://github.com/ruby/ruby/pull/4028 and included as a patch attached to this issue.

---Files--------------------------------
0001-Allow-ostruct-to-return-a-value-on-super.patch (1.7 KB)


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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>