From: "tenderlovemaking (Aaron Patterson) via ruby-core" <ruby-core@...>
Date: 2022-12-30T23:13:51+00:00
Subject: [ruby-core:111547] [Ruby master Bug#19278] Constructing subclasses of Data with positional arguments

Issue #19278 has been updated by tenderlovemaking (Aaron Patterson).


zverok (Victor Shepelev) wrote in #note-14:
> > Your example didn't demonstrate this difference.
> 
> > I really don't understand point 3. 
> 
> > To be honest, I don't really care anymore.
> 
> It is a pity, after the thread this long. 
> 
> If you would've cared, you'd maybe spent a few minutes drafting an `initialize` that would work the way you want **and maintained the contract**, and my points would probably become more obvious.

Sorry, I think you misunderstood.  I understand your points, I am just out of steam and don't care to continue the thread anymore.

Thanks.



----------------------------------------
Bug #19278: Constructing subclasses of Data with positional arguments
https://bugs.ruby-lang.org/issues/19278#change-100911

* Author: tenderlovemaking (Aaron Patterson)
* Status: Rejected
* Priority: Normal
* ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin22]
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
I'd expect both of the following subclasses to work, but the subclass that uses positional parameters raises an exception:

```ruby
Foo = Data.define

class Bar < Foo
  def initialize foo:
    p foo
  end
end

class Baz < Foo
  def initialize foo
    p foo
  end
end

Bar.new foo: 1 # Prints 1
Baz.new 1    # Raises ArgumentError
```

I'd expect the subclass that uses positional arguments to work.



-- 
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/